public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: misanjum@linux.ibm.com, NeilBrown <neilb@ownmail.net>,
	Jeff Layton <jlayton@kernel.org>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v1 0/2] Address UAF in sunrpc cache show callbacks
Date: Thu, 19 Feb 2026 16:50:15 -0500	[thread overview]
Message-ID: <20260219215017.1769-1-cel@kernel.org> (raw)

From: Chuck Lever <chuck.lever@oracle.com>

Attempt to address three crashes reported here:

https://lore.kernel.org/linux-nfs/dcd371d3a95815a84ba7de52cef447b8@linux.ibm.com/

These are compile-tested and regression-tested, but as I do not have
a PowerPC system handy, I will need someone who has one to test
whether they actually address the crashes.

Chuck Lever (2):
  NFSD: Defer sub-object cleanup in export put callbacks
  NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd

 fs/nfsd/export.c | 63 +++++++++++++++++++++++++++++++++++++++++-------
 fs/nfsd/export.h |  7 ++++--
 fs/nfsd/nfsctl.c | 22 ++++++++++++++---
 3 files changed, 78 insertions(+), 14 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-02-19 21:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19 21:50 Chuck Lever [this message]
2026-02-19 21:50 ` [PATCH v1 1/2] NFSD: Defer sub-object cleanup in export put callbacks Chuck Lever
2026-02-20 15:50   ` Jeff Layton
2026-02-25 18:29     ` Olga Kornievskaia
2026-02-25 18:53       ` Chuck Lever
2026-02-19 21:50 ` [PATCH v1 2/2] NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd Chuck Lever
2026-02-20 15:52   ` Jeff Layton
2026-02-25 18:29     ` Olga Kornievskaia
2026-02-21 22:57 ` [PATCH v1 0/2] Address UAF in sunrpc cache show callbacks NeilBrown
2026-02-22 15:41   ` Chuck Lever

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=20260219215017.1769-1-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=misanjum@linux.ibm.com \
    --cc=neilb@ownmail.net \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.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