From: Keith Busch <kbusch@kernel.org>
To: Daejun Park <daejun7.park@samsung.com>
Cc: "hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
"kch@nvidia.com" <kch@nvidia.com>,
"kanie@linux.alibaba.com" <kanie@linux.alibaba.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] nvmet: fix Reservation Acquire preempt sent by the holder
Date: Tue, 13 Oct 2026 09:37:37 -0600 [thread overview]
Message-ID: <as5QQbY2qa8Qq5N1@kbusch-mbp> (raw)
In-Reply-To: <20261002065931epcms2p1cb2c16f98cf3b05f8c859ad92b0ad465@epcms2p1>
On Fri, Oct 02, 2026 at 03:59:31PM +0900, Daejun Park wrote:
> nvmet_pr_preempt() does not follow NVMe Base Specification 2.1, section
> 8.1.22.7 when a Reservation Acquire command with the Preempt or Preempt
> and Abort action is sent by the reservation holder and the reservation
> is not of an All Registrants type.
>
> Patch 1 fixes a use-after-free read in the path that handles a preempt
> sent by the holder. It does not depend on patch 2 and comes first so
> that it can be backported alone.
>
> Patch 2: a holder that preempts with the key of another registrant gets
> a successful completion, but that registrant stays registered and the
> reservation type is changed to RTYPE. The pNFS SCSI layout server
> fences clients with this command (RFC 9561 section 2.2.3), so on an
> nvmet namespace nfsd logs a client as fenced while the client can still
> write to the device. The patch lists what changes for a host that
> holds the reservation.
Thanks, applied to nvme-7.4.
prev parent reply other threads:[~2026-10-13 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261002065931epcms2p1cb2c16f98cf3b05f8c859ad92b0ad465@epcms2p1>
2026-10-02 6:59 ` [PATCH 0/2] nvmet: fix Reservation Acquire preempt sent by the holder Daejun Park
2026-10-02 7:02 ` [PATCH 1/2] nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt() Daejun Park
2026-10-02 7:03 ` [PATCH 2/2] nvmet: fix preempt of another registrant by the reservation holder Daejun Park
2026-10-13 14:38 ` hch
2026-10-13 14:38 ` [PATCH 1/2] nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt() hch
2026-10-13 15:37 ` Keith Busch [this message]
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=as5QQbY2qa8Qq5N1@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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