From: James Morris <jmorris@namei.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov,
James Carter <jwcart2@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>,
spender@grsecurity.net, Daniel J Walsh <dwalsh@redhat.com>,
cl@linux-foundation.org, Arjan van de Ven <arjan@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
kees@outflux.net, Chad Sellers <csellers@tresys.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
"Serge E. Hallyn" <serue@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -v4 1/3] Capabilities: move cap_file_mmap to commoncap.c
Date: Wed, 5 Aug 2009 09:42:06 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.2.00.0908050938320.28805@tundra.namei.org> (raw)
In-Reply-To: <20090731165358.20992.14757.stgit@paris.rdu.redhat.com>
On Fri, 31 Jul 2009, Eric Paris wrote:
> Currently we duplicate the mmap_min_addr test in cap_file_mmap and in
> security_file_mmap if !CONFIG_SECURITY. This patch moves cap_file_mmap
> into commoncap.c and then calls that function directly from
> security_file_mmap ifndef CONFIG_SECURITY like all of the other capability
> checks are done.
These patches could do with more review / ack / signoff. Anyone? Bueller?
However, if there are no further comments, I'll likely apply these to
security-testing#next.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2009-08-04 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 16:53 Eric Paris
2009-07-31 16:54 ` [PATCH -v4 2/3] SELinux: call cap_file_mmap in selinux_file_mmap Eric Paris
2009-07-31 16:54 ` [PATCH -v4 3/3] Security/SELinux: seperate lsm specific mmap_min_addr Eric Paris
2009-08-04 23:42 ` James Morris [this message]
2009-08-06 0:19 ` [PATCH -v4 1/3] Capabilities: move cap_file_mmap to commoncap.c James Morris
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=alpine.LRH.2.00.0908050938320.28805@tundra.namei.org \
--to=jmorris@namei.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=cl@linux-foundation.org \
--cc=csellers@tresys.com \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=jwcart2@tycho.nsa.gov \
--cc=kees@outflux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serue@us.ibm.com \
--cc=spender@grsecurity.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®