linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: akpm@linux-foundation.org, 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, sds@tycho.nsa.gov
Subject: Re: [patch 04/11] vfs: introduce new LSM hooks where vfsmount is available.
Date: Sat, 6 Dec 2008 18:29:02 +0000	[thread overview]
Message-ID: <20081206182902.GP28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <200812062124.IEE78637.MFJFFOVSOtOHLQ@I-love.SAKURA.ne.jp>

On Sat, Dec 06, 2008 at 09:24:31PM +0900, Tetsuo Handa wrote:

> > 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.
> 
> do_sys_ftruncate() calls do_truncate() with "struct file *", whereas
> do_sys_truncate() and may_open() call do_truncate() with NULL.
> TOMOYO is not using the last argument, but I'm passing all arguments without
> modification so that a LSM module can know the last argument if that LSM module
> needs the last argument.

And if such a module ever shows up *and* its authors can give good reasons
for checks in that place that apply to ftruncate(2) but not to truncate(2),
we can always add such argument.  Until then...

Note that similar story with struct nameidata * being passed to fs methods
had caused a lot of mess and we are still not through with it.  Let's
stick to the things that make clear sense...

  reply	other threads:[~2008-12-06 18:29 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
2008-12-06 12:24   ` Tetsuo Handa
2008-12-06 18:29     ` Al Viro [this message]
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=20081206182902.GP28946@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).