From: Chuck Lever <chuck.lever@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>
Subject: Re: [PATCH] nfsd: Fix error cleanup path in nfsd_rename()
Date: Tue, 19 Mar 2024 11:18:15 -0400 [thread overview]
Message-ID: <Zfmst9GEpKwVVTaF@manet.1015granger.net> (raw)
In-Reply-To: <20240319135354.lyvyc7kvihp3kmt4@quack3>
On Tue, Mar 19, 2024 at 02:53:54PM +0100, Jan Kara wrote:
> On Mon 18-03-24 16:12:17, Chuck Lever wrote:
> > On Mon, Mar 18, 2024 at 05:32:09PM +0100, Jan Kara wrote:
> > > Commit a8b0026847b8 ("rename(): avoid a deadlock in the case of parents
> > > having no common ancestor") added an error bail out path. However this
> > > path does not drop the remount protection that has been acquired. Fix
> > > the cleanup path to properly drop the remount protection.
> > >
> > > Fixes: a8b0026847b8 ("rename(): avoid a deadlock in the case of parents having no common ancestor")
> > > Signed-off-by: Jan Kara <jack@suse.cz>
> >
> > Al, Jan, let me know if you'd like me to take this through the
> > nfsd tree for v6.9-rc. If not:
> >
> > Acked-by: Chuck Lever <chuck.lever@oracle.com>
>
> Yeah, I guess taking this through NFS tree is the best.
I've pushed this to my nfsd-fixes branch, and will begin testing.
> Honza
>
> >
> >
> > > ---
> > > fs/nfsd/vfs.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
> > > index 6a9464262fae..2e41eb4c3cec 100644
> > > --- a/fs/nfsd/vfs.c
> > > +++ b/fs/nfsd/vfs.c
> > > @@ -1852,7 +1852,7 @@ nfsd_rename(struct svc_rqst *rqstp, struct svc_fh *ffhp, char *fname, int flen,
> > > trap = lock_rename(tdentry, fdentry);
> > > if (IS_ERR(trap)) {
> > > err = (rqstp->rq_vers == 2) ? nfserr_acces : nfserr_xdev;
> > > - goto out;
> > > + goto out_want_write;
> > > }
> > > err = fh_fill_pre_attrs(ffhp);
> > > if (err != nfs_ok)
> > > @@ -1922,6 +1922,7 @@ nfsd_rename(struct svc_rqst *rqstp, struct svc_fh *ffhp, char *fname, int flen,
> > > }
> > > out_unlock:
> > > unlock_rename(tdentry, fdentry);
> > > +out_want_write:
> > > fh_drop_write(ffhp);
> > >
> > > /*
> > > --
> > > 2.35.3
> > >
> >
> > --
> > Chuck Lever
> >
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
--
Chuck Lever
next prev parent reply other threads:[~2024-03-19 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 16:32 [PATCH] nfsd: Fix error cleanup path in nfsd_rename() Jan Kara
2024-03-18 16:50 ` Jeff Layton
2024-03-18 20:12 ` Chuck Lever
2024-03-19 13:53 ` Jan Kara
2024-03-19 15:18 ` Chuck Lever [this message]
2024-03-22 2:37 ` 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=Zfmst9GEpKwVVTaF@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-nfs@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