Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	Wang Yugui <wangyugui@e16-tech.com>,
	Trond Myklebust <trondmy@hammerspace.com>,
	Stanislav Saner <ssaner@redhat.com>,
	Ruben Vestergaard <rubenv@drcmr.dk>,
	Torkil Svensgaard <torkil@drcmr.dk>
Subject: Re: [PATCH] nfsd: fix handling of cached open files in nfsd4_open codepath
Date: Fri, 06 Jan 2023 13:15:31 -0500	[thread overview]
Message-ID: <ed66d0c4bd454e7a3f17038a735a99a00390833f.camel@kernel.org> (raw)
In-Reply-To: <BC8EF64C-3F08-4E10-B562-344FFD1D37B2@oracle.com>

On Fri, 2023-01-06 at 17:56 +0000, Chuck Lever III wrote:
> 
> > On Jan 5, 2023, at 2:55 PM, Jeff Layton <jlayton@kernel.org> wrote:
> > 
> > Commit fb70bf124b05 ("NFSD: Instantiate a struct file when creating a
> > regular NFSv4 file") added the ability to cache an open fd over a
> > compound. There are a couple of problems with the way this currently
> > works:
> > 
> > It's racy, as a newly-created nfsd_file can end up with its PENDING bit
> > cleared while the nf is hashed, and the nf_file pointer is still zeroed
> > out. Other tasks can find it in this state and they expect to see a
> > valid nf_file, and can oops if nf_file is NULL.
> > 
> > Also, there is no guarantee that we'll end up creating a new nfsd_file
> > if one is already in the hash. If an extant entry is in the hash with a
> > valid nf_file, nfs4_get_vfs_file will clobber its nf_file pointer with
> > the value of op_file and the old nf_file will leak.
> > 
> > Fix both issues by making a new nfsd_file_acquirei_opened variant that
> > takes an optional file pointer. If one is present when this is called,
> > we'll take a new reference to it instead of trying to open the file. If
> > the nfsd_file already has a valid nf_file, we'll just ignore the
> > optional file and pass the nfsd_file back as-is.
> > 
> > Also rework the tracepoints a bit to allow for an "opened" variant and
> > don't try to avoid counting acquisitions in the case where we already
> > have a cached open file.
> > 
> > Fixes: fb70bf124b05 ("NFSD: Instantiate a struct file when creating a regular NFSv4 file")
> > Cc: Trond Myklebust <trondmy@hammerspace.com>
> > Reported-by: Stanislav Saner <ssaner@redhat.com>
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > fs/nfsd/filecache.c | 40 ++++++++++++++++++----------------
> > fs/nfsd/filecache.h |  5 +++--
> > fs/nfsd/nfs4state.c | 16 ++++----------
> > fs/nfsd/trace.h     | 52 ++++++++++++---------------------------------
> > 4 files changed, 42 insertions(+), 71 deletions(-)
> > 
> > v3: add new nfsd_file_acquire_opened variant instead of changing
> >    nfsd_file_acquire prototype
> 
> Hi Jeff, v3 applied to nfsd's for-rc.
> 

Can you also add:

    Reported-and-Tested-by: Ruben Vestergaard    rubenv@drcmr.dk
    Reported-and-Tested-by: Torkil Svensgaard    torkil@drcmr.dk

They've been helping test these patches (albeit backported versions on a
RHEL9 kernel), and reported the crash that helped me track this down.

Many thanks!
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2023-01-06 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 19:55 [PATCH] nfsd: fix handling of cached open files in nfsd4_open codepath Jeff Layton
2023-01-06 17:56 ` Chuck Lever III
2023-01-06 18:15   ` Jeff Layton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-04 23:11 Jeff Layton

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=ed66d0c4bd454e7a3f17038a735a99a00390833f.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dhowells@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rubenv@drcmr.dk \
    --cc=ssaner@redhat.com \
    --cc=torkil@drcmr.dk \
    --cc=trondmy@hammerspace.com \
    --cc=wangyugui@e16-tech.com \
    /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