Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neil@brown.name>, Chuck Lever <chuck.lever@oracle.com>,
	Mike Snitzer <snitzer@kernel.org>
Cc: Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna.schumaker@oracle.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2 RFT] nfsd: fix another problem with recent localio changes
Date: Fri, 18 Jul 2025 07:52:53 -0400	[thread overview]
Message-ID: <a9c15e1e3a72d616bd5e8b9e64616a316d5d06b8.camel@kernel.org> (raw)
In-Reply-To: <20250718012831.2187613-1-neil@brown.name>

On Fri, 2025-07-18 at 11:26 +1000, NeilBrown wrote:
> Mike reports ongoing problem with leakage of refcounts for the net in
> nfsd when localio is used.  I believe the first patch fixes one possible
> cause.  The second patch removes some related dead code.
> 
> Mike: thanks for your testing so far.  Hopefully you could find time to
> test this one too?
> 
> Thanks,
> NeilBrown
> 
>  [PATCH 1/2] nfsd: avoid ref leak in nfsd_open_local_fh()
>  [PATCH 2/2] nfsd: discard nfsd_file_get_local()

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  parent reply	other threads:[~2025-07-18 11:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  1:26 [PATCH 0/2 RFT] nfsd: fix another problem with recent localio changes NeilBrown
2025-07-18  1:26 ` [PATCH 1/2] nfsd: avoid ref leak in nfsd_open_local_fh() NeilBrown
2025-07-18  2:37   ` Mike Snitzer
2025-07-18  3:00     ` NeilBrown
2025-07-18  1:26 ` [PATCH 2/2] nfsd: discard nfsd_file_get_local() NeilBrown
2025-07-18  2:37   ` Mike Snitzer
2025-07-18 11:52 ` Jeff Layton [this message]
2025-07-18 14:25 ` [PATCH 0/2 RFT] nfsd: fix another problem with recent localio changes Chuck Lever
2025-07-18 14:27   ` Mike Snitzer
2025-07-18 14:36     ` Mike Snitzer

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=a9c15e1e3a72d616bd5e8b9e64616a316d5d06b8.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=anna.schumaker@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=snitzer@kernel.org \
    --cc=trondmy@kernel.org \
    /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