From: Al Viro <viro@ZenIV.linux.org.uk>
To: akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, takedakn@nttdata.co.jp,
casey@schaufler-ca.com, crispin@crispincowan.com,
haradats@nttdata.co.jp, hch@lst.de, jmorris@namei.org,
penguin-kernel@I-love.SAKURA.ne.jp, sds@tycho.nsa.gov
Subject: Re: [patch 04/11] vfs: introduce new LSM hooks where vfsmount is available.
Date: Sat, 6 Dec 2008 07:10:09 +0000 [thread overview]
Message-ID: <20081206071009.GO28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <200812012234.mB1MYsqc021084@imap1.linux-foundation.org>
On Mon, Dec 01, 2008 at 02:34:54PM -0800, akpm@linux-foundation.org wrote:
In principle, ACK.
> fs/namei.c | 37 +++++++++
> fs/open.c | 5 +
> include/linux/security.h | 139 +++++++++++++++++++++++++++++++++++++
> net/unix/af_unix.c | 4 +
> security/Kconfig | 9 ++
> security/capability.c | 57 +++++++++++++++
> security/security.c | 66 +++++++++++++++++
> 7 files changed, 317 insertions(+)
>
> diff -puN fs/namei.c~introduce-new-lsm-hooks-where-vfsmount-is-available fs/namei.c
> --- a/fs/namei.c~introduce-new-lsm-hooks-where-vfsmount-is-available
> +++ a/fs/namei.c
> @@ -1556,6 +1556,10 @@ int may_open(struct nameidata *nd, int a
> * Refuse to truncate files with mandatory locks held on them.
> */
> error = locks_verify_locked(inode);
> + if (!error)
> + error = security_path_truncate(&nd->path, 0,
> + ATTR_MTIME|ATTR_CTIME|ATTR_OPEN,
> + NULL);
Humm... What's the story with the last argument (struct file *) in there?
Explain that and you've got it merged; other than this part I have no
objections to that patch.
next prev parent reply other threads:[~2008-12-06 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 22:34 [patch 04/11] vfs: introduce new LSM hooks where vfsmount is available akpm
2008-12-06 7:10 ` Al Viro [this message]
2008-12-06 12:24 ` Tetsuo Handa
2008-12-06 18:29 ` Al Viro
2008-12-08 1:33 ` Kentaro Takeda
2008-12-12 1:59 ` Kentaro Takeda
2008-12-16 1:12 ` Kentaro Takeda
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=20081206071009.GO28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--cc=crispin@crispincowan.com \
--cc=haradats@nttdata.co.jp \
--cc=hch@lst.de \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=takedakn@nttdata.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).