From: Dan Rosenberg <drosenberg@vsecurity.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] kptr_restrict for hiding kernel pointers from unprivileged users
Date: Thu, 09 Dec 2010 21:45:18 -0500 [thread overview]
Message-ID: <1291949118.1877.2.camel@dan> (raw)
In-Reply-To: <1291901420.4063.24.camel@edumazet-laptop>
>
> Well, it seems difficult to make a check here, its a generic function
> that happens to be used from different contexts.
>
> Even using in_irq() might be a problem.
I agree it seems difficult - my only goal was to prevent subsequent
breakage with the capability check. Does anyone have any suggestions
for a better approach here?
-Dan
next prev parent reply other threads:[~2010-12-10 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 3:05 [PATCH] kptr_restrict for hiding kernel pointers from unprivileged users Dan Rosenberg
2010-12-09 3:23 ` Eric Dumazet
2010-12-09 3:26 ` Eric Dumazet
2010-12-09 11:51 ` Dan Rosenberg
2010-12-09 12:46 ` Dan Rosenberg
2010-12-09 13:30 ` Eric Dumazet
2010-12-09 13:30 ` Eric Dumazet
2010-12-10 2:45 ` Dan Rosenberg [this message]
2010-12-10 16:05 ` Peter Zijlstra
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=1291949118.1877.2.camel@dan \
--to=drosenberg@vsecurity.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.