From: "Chuck Lever" <cel@kernel.org>
To: "Christoph Hellwig" <hch@infradead.org>
Cc: 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>,
linux-nfs@vger.kernel.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: Re: [PATCH v5] NFSD: Track SCSI Persistent Registration Fencing per Client with xarray
Date: Wed, 07 Jan 2026 19:26:26 -0500 [thread overview]
Message-ID: <9e127bfa-e4c9-4e06-b5ad-bb375e7d8e2b@app.fastmail.com> (raw)
In-Reply-To: <aV6HHwrkoR4OE5qc@infradead.org>
On Wed, Jan 7, 2026, at 11:17 AM, Christoph Hellwig wrote:
> On Fri, Dec 26, 2025 at 11:24:37PM -0500, Chuck Lever wrote:
>
>> @@ -342,6 +343,20 @@ nfsd4_block_get_device_info_scsi(struct super_block *sb,
>> goto out_free_dev;
>> }
>>
>> + /*
>> + * xa_store() is idempotent -- the device is added exactly once
>> + * to a client's cl_dev_fences no matter how many times
>> + * nfsd4_block_get_device_info_scsi() is invoked. This prevents
>> + * adding more entries to cl_dev_fences than there are devices on
>> + * the server. XA_MARK_0 tracks whether the device has been fenced.
>> + */
>
> Only in the most abstract way, xa_store actually stores the new
> entry/value and returns the old one. In other words, this does
> quite a bit of work for the non-initial GETDEVICEINFO.
The comment is misleading then, and should be clarified.
But should the code use xa_insert instead of xa_store ?
--
Chuck Lever
next prev parent reply other threads:[~2026-01-08 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 4:24 [PATCH v5] NFSD: Track SCSI Persistent Registration Fencing per Client with xarray Chuck Lever
2026-01-03 19:46 ` Dai Ngo
2026-01-07 16:17 ` Christoph Hellwig
2026-01-08 0:26 ` Chuck Lever [this message]
2026-01-08 0:56 ` NeilBrown
2026-01-08 9:26 ` Christoph Hellwig
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=9e127bfa-e4c9-4e06-b5ad-bb375e7d8e2b@app.fastmail.com \
--to=cel@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@ownmail.net \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.