From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
ezk@cs.sunysb.edu, akpm@osdl.org, linux-kernel@vger.kernel.org,
hch@infradead.org
Subject: Re: [PATCH 2/2] fix up new filp allocators
Date: Fri, 9 Nov 2007 16:46:21 -0500 [thread overview]
Message-ID: <20071109214621.GK26826@fieldses.org> (raw)
In-Reply-To: <1194644122.7078.116.camel@localhost>
On Fri, Nov 09, 2007 at 01:35:22PM -0800, Dave Hansen wrote:
> On Fri, 2007-11-09 at 16:26 -0500, Trond Myklebust wrote:
> > > #include <linux/sunrpc/svc.h>
> > > #include <linux/nfsd/nfsd.h>
> > > #include <linux/nfsd/cache.h>
> > > +#include <linux/file.h>
> > > #include <linux/mount.h>
> > > #include <linux/workqueue.h>
> > > #include <linux/smp_lock.h>
> > > @@ -1303,7 +1304,7 @@ static inline void
> > > nfs4_file_downgrade(struct file *filp, unsigned int share_access)
> > > {
> > > if (share_access & NFS4_SHARE_ACCESS_WRITE) {
> > > - put_write_access(filp->f_path.dentry->d_inode);
> > > + drop_file_write_access(filp);
> > > filp->f_mode = (filp->f_mode | FMODE_READ) & ~FMODE_WRITE;
> > > }
> > > }
> >
> > Hmm... The NFS server may also try to 'upgrade' an open file request to
> > a read/write request whenever the client issues a new OPEN request for
> > WRITE using the same open_owner.
>
> Can you point me to some code? I'll try and go fix it up.
See fs/nfsd/nfs4state.c:nfs4_upgrade_open().
I suspect that there are other reasons why what nfsd is doing here is a
bad idea, and that we should really be getting a new file descriptor.
But I haven't figured out yet what to do instead.
--b.
next prev parent reply other threads:[~2007-11-09 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 21:04 [PATCH 1/2] create file_drop_write_access() helper Dave Hansen
2007-11-09 21:04 ` [PATCH 2/2] fix up new filp allocators Dave Hansen
2007-11-09 21:26 ` Trond Myklebust
2007-11-09 21:35 ` Dave Hansen
2007-11-09 21:46 ` J. Bruce Fields [this message]
2007-11-10 2:36 ` [PATCH 1/2] create file_drop_write_access() helper Erez Zadok
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=20071109214621.GK26826@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@osdl.org \
--cc=ezk@cs.sunysb.edu \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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