From: Keith Busch <kbusch@kernel.org>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: hch@lst.de, harimishal1@gmail.com, sagi@grimberg.me,
linux-nvme@lists.infradead.org, gregkh@linuxfoundation.org,
gost.dev@samsung.com
Subject: Re: [PATCH v2 0/2] fix racy access to FDP placement id array
Date: Wed, 19 Aug 2026 09:33:07 -0600 [thread overview]
Message-ID: <aoXMs3EORQugrJzU@kbusch-mbp> (raw)
In-Reply-To: <20260818060253.4104-1-joshi.k@samsung.com>
On Tue, Aug 18, 2026 at 11:32:51AM +0530, Kanchan Joshi wrote:
> Patch 1: prep to send non-admin commands from nvme_alloc_ns_head
> Patch 2: avoid the race by moving fdp registration to nvme_alloc_ns_head
Thanks, applied to nvme-7.3.
prev parent reply other threads:[~2026-08-19 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260818060330epcas5p4556a447149a5c2cd1e9aadd64952c01d@epcas5p4.samsung.com>
2026-08-18 6:02 ` [PATCH v2 0/2] fix racy access to FDP placement id array Kanchan Joshi
2026-08-18 6:02 ` [PATCH v2 1/2] nvme: set ns->head in nvme_alloc_ns_head Kanchan Joshi
2026-08-19 5:36 ` Christoph Hellwig
2026-08-18 6:02 ` [PATCH v2 2/2] nvme: fix racy access to FDP placement id array Kanchan Joshi
2026-08-19 5:36 ` Christoph Hellwig
2026-08-19 15:33 ` 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=aoXMs3EORQugrJzU@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=gost.dev@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=harimishal1@gmail.com \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--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