From: Nick Piggin <npiggin@suse.de>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, akpm <akpm@linuxfoundation.org>
Subject: Re: mnt_want_write_file() has problem?
Date: Wed, 5 Aug 2009 07:37:05 +0200 [thread overview]
Message-ID: <20090805053705.GA11060@wotan.suse.de> (raw)
In-Reply-To: <1249413319.11056.131.camel@nimitz>
On Tue, Aug 04, 2009 at 12:15:19PM -0700, Dave Hansen wrote:
> On Mon, 2009-08-03 at 06:36 +0900, OGAWA Hirofumi wrote:
> > diff -puN fs/namespace.c~mnt_want_write-wrong-assume fs/namespace.c
> > ---
> > linux-2.6/fs/namespace.c~mnt_want_write-wrong-assume 2009-08-03
> > 04:33:35.000000000 +0900
> > +++ linux-2.6-hirofumi/fs/namespace.c 2009-08-03 04:31:34.000000000
> > +0900
> > @@ -316,7 +316,8 @@ EXPORT_SYMBOL_GPL(mnt_clone_write);
> > */
> > int mnt_want_write_file(struct file *file)
> > {
> > - if (!(file->f_mode & FMODE_WRITE))
> > + struct inode *inode = file->f_dentry->d_inode;
> > + if (!(file->f_mode & FMODE_WRITE) || special_file(inode->i_mode))
> > return mnt_want_write(file->f_path.mnt);
> > else
> > return mnt_clone_write(file->f_path.mnt);
>
> I'm fine with this. I'd like a debugging check in mnt_clone_write()
> since this bug is easy to detect, but such a check will also cost all of
> the performance gains that Nick added. So, we can't have it
> unconditionally.
Yeah, good catch, thanks for this.
next prev parent reply other threads:[~2009-08-05 5:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 21:36 mnt_want_write_file() has problem? OGAWA Hirofumi
2009-08-03 18:31 ` Dave Hansen
2009-08-03 18:48 ` OGAWA Hirofumi
2009-08-03 20:37 ` Dave Hansen
2009-08-04 19:15 ` Dave Hansen
2009-08-05 5:37 ` Nick Piggin [this message]
2009-09-12 13:39 ` Al Viro
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=20090805053705.GA11060@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linuxfoundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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