From: Ingo Molnar <mingo@elte•hu>
To: Dan Rosenberg <drosenberg@vsecurity•com>
Cc: linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
linux-security-module@vger•kernel.org, jmorris@namei•org,
eric.dumazet@gmail•com, tgraf@infradead•org,
eugeneteo@kernel•org, kees.cook@canonical•com,
davem@davemloft•net, a.p.zijlstra@chello•nl,
akpm@linux-foundation•org, eparis@parisplace•org
Subject: Re: [PATCH v5] kptr_restrict for hiding kernel pointers
Date: Wed, 22 Dec 2010 18:13:07 +0100 [thread overview]
Message-ID: <20101222171307.GA25611@elte.hu> (raw)
In-Reply-To: <1293037246.9820.236.camel@dan>
* Dan Rosenberg <drosenberg@vsecurity•com> wrote:
> + case 'K':
> + /*
> + * %pK cannot be used in IRQ context because its test
> + * for CAP_SYSLOG would be meaningless.
> + */
> + if (in_irq() || in_serving_softirq() || in_nmi())
> + WARN_ONCE(1, "%%pK used in interrupt context.\n");
Hm, that bit looks possibly broken - some useful warning in irq context could print
a pointer into the syslog and this would generate a second warning? That probably
would crash as it recurses back into the printk code?
Instead a warning could be inserted into the generated output instead, for example
'pK-error' (carefully staying within pointer length limits).
Also, it would be nice to see a couple of actual %pK usage sites submitted as well -
instead of this pure infrastructure patch.
Ingo
next prev parent reply other threads:[~2010-12-22 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 17:00 [PATCH v5] kptr_restrict for hiding kernel pointers Dan Rosenberg
2010-12-22 17:13 ` Ingo Molnar [this message]
2010-12-22 17:17 ` Dan Rosenberg
2010-12-22 17:19 ` Dan Rosenberg
2010-12-22 21:43 ` Valdis.Kletnieks
2010-12-22 17:35 ` Dan Rosenberg
2010-12-22 21:26 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101222171307.GA25611@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=a.p.zijlstra@chello$(echo .)nl \
--cc=akpm@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=drosenberg@vsecurity$(echo .)com \
--cc=eparis@parisplace$(echo .)org \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=eugeneteo@kernel$(echo .)org \
--cc=jmorris@namei$(echo .)org \
--cc=kees.cook@canonical$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tgraf@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox