From: Dai Ngo <dai.ngo@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org, Trond Myklebust <trondmy@kernel.org>,
anna@kernel.org
Subject: Re: [PATCH v3 1/1] pNFS: Serialize SCSI PR registration to avoid reservation conflicts
Date: Mon, 9 Mar 2026 09:38:46 -0700 [thread overview]
Message-ID: <ebe57216-1c17-4b9d-8a2d-6e2a09bdcbc9@oracle.com> (raw)
In-Reply-To: <aa7oo3sOTe-WKjVl@infradead.org>
On 3/9/26 8:34 AM, Christoph Hellwig wrote:
> On Fri, Mar 06, 2026 at 10:46:00AM -0800, Dai Ngo wrote:
>> Christoph,
>>
>> The new mutex, pbd_registration_mutex, is initialized only for the
>> top-level pnfs_block_dev in this patch. The mutexes for child pnfs_block_dev
>> instances allocated by bl_parse_concat() and bl_parse_stripe() are not
>> initialized.
>>
>> Should we initialize these child mutexes as well, in case we later want
>> to support concatenated and striped SCSI devices for pNFS?
> I don't think we need to, as the registration would happen on the
> actual SCSI devices, not the meta devices.
ok, thanks!
-Dai
prev parent reply other threads:[~2026-03-09 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 16:29 [PATCH v3 1/1] pNFS: Serialize SCSI PR registration to avoid reservation conflicts Dai Ngo
2026-03-06 18:46 ` Dai Ngo
2026-03-09 15:34 ` Christoph Hellwig
2026-03-09 16:38 ` Dai Ngo [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=ebe57216-1c17-4b9d-8a2d-6e2a09bdcbc9@oracle.com \
--to=dai.ngo@oracle.com \
--cc=anna@kernel.org \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.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