From: "J.Bruce Fields" <bfields@citi.umich.edu>
To: Harshula Jayasuriya <harshula@redhat.com>
Cc: linux-nfs@vger.kernel.org, NeilBrown <neilb@suse.de>
Subject: Re: [PATCH] nfsd: nfs4_file_get_access: need to be more careful with O_RDWR
Date: Tue, 23 Jul 2013 12:28:13 -0400 [thread overview]
Message-ID: <20130723162813.GC12569@fieldses.org> (raw)
In-Reply-To: <1374552314.5454.89.camel@serendib>
Thanks, applying for 3.12.--b.
On Tue, Jul 23, 2013 at 02:05:14PM +1000, Harshula Jayasuriya wrote:
> If fi_fds = {non-NULL, NULL, non-NULL} and oflag = O_WRONLY
> the WARN_ON_ONCE(!(fp->fi_fds[oflag] || fp->fi_fds[O_RDWR]))
> doesn't trigger when it should.
>
> Signed-off-by: Harshula Jayasuriya <harshula@redhat.com>
> ---
> fs/nfsd/nfs4state.c | 13 ++++---------
> 1 file changed, 4 insertions(+), 9 deletions(-)
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 280acef..1cb6211 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -282,19 +282,14 @@ static unsigned int file_hashval(struct inode *ino)
>
> static struct hlist_head file_hashtbl[FILE_HASH_SIZE];
>
> -static void __nfs4_file_get_access(struct nfs4_file *fp, int oflag)
> -{
> - WARN_ON_ONCE(!(fp->fi_fds[oflag] || fp->fi_fds[O_RDWR]));
> - atomic_inc(&fp->fi_access[oflag]);
> -}
> -
> static void nfs4_file_get_access(struct nfs4_file *fp, int oflag)
> {
> + WARN_ON_ONCE(!fp->fi_fds[oflag]);
> if (oflag == O_RDWR) {
> - __nfs4_file_get_access(fp, O_RDONLY);
> - __nfs4_file_get_access(fp, O_WRONLY);
> + atomic_inc(&fp->fi_access[O_RDONLY]);
> + atomic_inc(&fp->fi_access[O_WRONLY]);
> } else
> - __nfs4_file_get_access(fp, oflag);
> + atomic_inc(&fp->fi_access[oflag]);
> }
>
> static void nfs4_file_put_fd(struct nfs4_file *fp, int oflag)
> --
> 1.8.1.4
>
prev parent reply other threads:[~2013-07-23 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 4:05 [PATCH] nfsd: nfs4_file_get_access: need to be more careful with O_RDWR Harshula Jayasuriya
2013-07-23 16:28 ` J.Bruce Fields [this message]
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=20130723162813.GC12569@fieldses.org \
--to=bfields@citi.umich.edu \
--cc=harshula@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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).