From: Christoph Hellwig <hch@lst.de>
To: Dai Ngo <dai.ngo@oracle.com>
Cc: chuck.lever@oracle.com, jlayton@kernel.org, neilb@ownmail.net,
okorniev@redhat.com, tom@talpey.com, hch@lst.de,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 1/2] NFSD: Fix problem with nfsd4_scsi_fence_client using the wrong reservation type
Date: Wed, 5 Nov 2025 14:21:37 +0100 [thread overview]
Message-ID: <20251105132137.GA19612@lst.de> (raw)
In-Reply-To: <20251104173103.2893787-2-dai.ngo@oracle.com>
Maybe reword the title as:
NFSD: use correcvt reservation type in nfsd4_scsi_fence_client
The fact that it wasn't correct before pretty much implies that there
was a problem :)
Otherwise looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-11-05 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 17:27 [PATCH v2 0/2] NFSD: Fix problem with nfsd4_scsi_fence_client Dai Ngo
2025-11-04 17:27 ` [PATCH v2 1/2] NFSD: Fix problem with nfsd4_scsi_fence_client using the wrong reservation type Dai Ngo
2025-11-05 13:21 ` Christoph Hellwig [this message]
2025-11-04 17:27 ` [PATCH v2 2/2] NFSD: Add trace point for SCSI fencing operation Dai Ngo
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=20251105132137.GA19612@lst.de \
--to=hch@lst.de \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).