All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman@suse.de>
To: Neil Brown <neilb@suse.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfsd: Fix possible BUG_ON firing in set_change_info
Date: Thu, 02 Dec 2010 12:22:16 +0530	[thread overview]
Message-ID: <4CF74220.9050109@suse.de> (raw)
In-Reply-To: <20101202111430.57275603-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>

On 12/02/2010 05:44 AM, Neil Brown wrote:
> 
> If vfs_getattr in fill_post_wcc returns an error, we don't
> set fh_post_change.
> For NFSv4, this can result in set_change_info triggering a BUG_ON.
> i.e. fh_post_saved being zero isn't really a bug.
> 
> So:
>  - instead of BUGging when fh_post_saved is zero, just clear ->atomic.
>  - if vfs_getattr fails in fill_post_wcc, take a copy of i_ctime anyway.
>    This will be used i seg_change_info, but not overly trusted.
>  - While we are there, remove the pointless 'if' statements in set_change_info.
>    There is no harm setting all the values.
> 
> Signed-off-by: NeilBrown <neilb@suse.de>
> 
> --
> 
> If you think the code is clearer with the if() structure, feel free
> to leave that part unchanged.
> 
> NeilBrown
> 
> diff --git a/fs/nfsd/nfs3xdr.c b/fs/nfsd/nfs3xdr.c
> index 2a533a0..7e84a85 100644
> --- a/fs/nfsd/nfs3xdr.c
> +++ b/fs/nfsd/nfs3xdr.c
> @@ -260,9 +260,11 @@ void fill_post_wcc(struct svc_fh *fhp)
>  	err = vfs_getattr(fhp->fh_export->ex_path.mnt, fhp->fh_dentry,
>  			&fhp->fh_post_attr);
>  	fhp->fh_post_change = fhp->fh_dentry->d_inode->i_version;
> -	if (err)
> +	if (err) {
>  		fhp->fh_post_saved = 0;
> -	else
> +		/* Grab the ctime anyway - set_change_info might use it */
> +		fhp->fh_post_attr.ctime = fhp->fh_dentry->d_inode->i_ctime;

Perhaps, a dprintk here would help debugging?


Thanks,

-- 
Suresh Jayaraman

  parent reply	other threads:[~2010-12-02  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101202111430.57275603@notabene.brown>
2010-12-02  6:20 ` [PATCH] nfsd: Fix possible BUG_ON firing in set_change_info Suresh Jayaraman
2010-12-08  1:12   ` J. Bruce Fields
     [not found] ` <20101202111430.57275603-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2010-12-02  6:52   ` Suresh Jayaraman [this message]
2010-12-11  0:15 ` J.Bruce Fields

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=4CF74220.9050109@suse.de \
    --to=sjayaraman@suse.de \
    --cc=bfields@fieldses.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.