public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	npiggin@kernel.dk, shaohua.li@intel.com, sds@tycho.nsa.gov,
	jmorris@namei.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH 1/3] SECURITY: Move exec_permission RCU checks into security modules
Date: Fri, 22 Apr 2011 08:25:20 -0700	[thread overview]
Message-ID: <20110422152520.GB10755@tassilo.jf.intel.com> (raw)
In-Reply-To: <20110422043444.GA9038@infradead.org>

> This seems to miss the hunk in fs/namei.c where the LSM hook is called.

namei.c doesn't need changes because it already passes in the flags
The changed semantics only "start" in security/security.c

Thanks for review.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

  reply	other threads:[~2011-04-22 15:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22  0:23 Make RCU dcache work with CONFIG_SECURITY=y Andi Kleen
2011-04-22  0:23 ` [PATCH 1/3] SECURITY: Move exec_permission RCU checks into security modules Andi Kleen
2011-04-22  0:46   ` Eric Paris
2011-04-22  4:34   ` Christoph Hellwig
2011-04-22 15:25     ` Andi Kleen [this message]
2011-04-22 15:27       ` Christoph Hellwig
2011-04-22  0:23 ` [PATCH 2/3] SELINUX: Make selinux cache VFS RCU walks safe Andi Kleen
2011-04-22  0:45   ` Eric Paris
2011-04-22 15:16     ` Andi Kleen
2011-04-22  0:23 ` [PATCH 3/3] SMACK: Make smack directory access check RCU safe Andi Kleen
2011-04-22  1:40 ` Make RCU dcache work with CONFIG_SECURITY=y Shaohua Li
2011-04-22 18:26 ` Linus Torvalds
2011-04-22 21:16   ` Andi Kleen
2011-04-22 21:32     ` Casey Schaufler
2011-04-22 21:17   ` Eric Paris
2011-04-22 23:29     ` Linus Torvalds

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=20110422152520.GB10755@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=hch@infradead.org \
    --cc=jmorris@namei.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    --cc=sds@tycho.nsa.gov \
    --cc=shaohua.li@intel.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox