All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael.christie@oracle.com
To: Hannes Reinecke <hare@suse.de>, Keith Busch <kbusch@kernel.org>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
	snitzer@kernel.org, hch@lst.de, axboe@kernel.dk,
	martin.petersen@oracle.com,
	james.bottomley@hansenpartnership.com,
	linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH 09/11] block, nvme: Add error for reservation conflicts.
Date: Sat, 4 Jun 2022 12:13:50 -0500	[thread overview]
Message-ID: <6cc818cf-fac4-d485-ea9d-0b8597f24a33@oracle.com> (raw)
In-Reply-To: <fdd77f3b-691a-a9bf-b31f-0aa845e68e59@suse.de>

On 6/4/22 2:38 AM, Hannes Reinecke wrote:
> On 6/3/22 21:45, Keith Busch wrote:
>> On Fri, Jun 03, 2022 at 01:55:34AM -0500, Mike Christie wrote:
>>> @@ -171,6 +171,7 @@ static const struct {
>>>       /* zone device specific errors */
>>>       [BLK_STS_ZONE_OPEN_RESOURCE]    = { -ETOOMANYREFS, "open zones exceeded" },
>>>       [BLK_STS_ZONE_ACTIVE_RESOURCE]    = { -EOVERFLOW, "active zones exceeded" },
>>> +    [BLK_STS_RSV_CONFLICT]    = { -EBADE,    "resevation conflict" },
>>
>> You misspelled "reservation". :)
>>
>> And since you want a different error, why reuse EBADE for the errno? That is
>> already used for BLK_STS_NEXUS that you're trying to differentiate from, right?
>> At least for nvme, this error code is returned when the host lacks sufficient
>> rights, so something like EACCESS might make sense.
>>
>> Looks good otherwise.
> 
> Welll ... BLK_STS_NEXUS _is_ the reservation error.

I was not sure of xen/virtio scsi uses of BLK_STS_NEXUS/DID_NEXUS_FAILURE.
The virtio spec's description for VIRTIO_SCSI_S_NEXUS_FAILURE:

    if the nexus is suffering a failure but retrying on other paths might
    yield a different result. 

looks like the description for DID_NEXUS_FAILURE in scsi_status.h.
To me the the description sounded generic where it could used for
other errors like the endpoint/port for the I_T is removed.

However, the qemu code only uses VIRTIO_SCSI_S_NEXUS_FAILURE for
reservation conflicts. If we are saying that is always the case in
other virt implementations, I don't even need this patch :) and we
can do what you requested and do more of a rename.

WARNING: multiple messages have this Message-ID (diff)
From: michael.christie@oracle.com
To: Hannes Reinecke <hare@suse.de>, Keith Busch <kbusch@kernel.org>
Cc: axboe@kernel.dk, james.bottomley@hansenpartnership.com,
	linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
	snitzer@kernel.org, linux-block@vger.kernel.org,
	dm-devel@redhat.com, target-devel@vger.kernel.org, hch@lst.de
Subject: Re: [dm-devel] [PATCH 09/11] block, nvme: Add error for reservation conflicts.
Date: Sat, 4 Jun 2022 12:13:50 -0500	[thread overview]
Message-ID: <6cc818cf-fac4-d485-ea9d-0b8597f24a33@oracle.com> (raw)
In-Reply-To: <fdd77f3b-691a-a9bf-b31f-0aa845e68e59@suse.de>

On 6/4/22 2:38 AM, Hannes Reinecke wrote:
> On 6/3/22 21:45, Keith Busch wrote:
>> On Fri, Jun 03, 2022 at 01:55:34AM -0500, Mike Christie wrote:
>>> @@ -171,6 +171,7 @@ static const struct {
>>>       /* zone device specific errors */
>>>       [BLK_STS_ZONE_OPEN_RESOURCE]    = { -ETOOMANYREFS, "open zones exceeded" },
>>>       [BLK_STS_ZONE_ACTIVE_RESOURCE]    = { -EOVERFLOW, "active zones exceeded" },
>>> +    [BLK_STS_RSV_CONFLICT]    = { -EBADE,    "resevation conflict" },
>>
>> You misspelled "reservation". :)
>>
>> And since you want a different error, why reuse EBADE for the errno? That is
>> already used for BLK_STS_NEXUS that you're trying to differentiate from, right?
>> At least for nvme, this error code is returned when the host lacks sufficient
>> rights, so something like EACCESS might make sense.
>>
>> Looks good otherwise.
> 
> Welll ... BLK_STS_NEXUS _is_ the reservation error.

I was not sure of xen/virtio scsi uses of BLK_STS_NEXUS/DID_NEXUS_FAILURE.
The virtio spec's description for VIRTIO_SCSI_S_NEXUS_FAILURE:

    if the nexus is suffering a failure but retrying on other paths might
    yield a different result. 

looks like the description for DID_NEXUS_FAILURE in scsi_status.h.
To me the the description sounded generic where it could used for
other errors like the endpoint/port for the I_T is removed.

However, the qemu code only uses VIRTIO_SCSI_S_NEXUS_FAILURE for
reservation conflicts. If we are saying that is always the case in
other virt implementations, I don't even need this patch :) and we
can do what you requested and do more of a rename.

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2022-06-04 17:14 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  6:55 [PATCH 0/8] Use block pr_ops in LIO Mike Christie
2022-06-03  6:55 ` [dm-devel] " Mike Christie
2022-06-03  6:55 ` [PATCH 01/11] scsi: target: Rename sbc_ops to exec_cmd_ops Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-20  7:12   ` Christoph Hellwig
2022-06-20  7:12     ` [dm-devel] " Christoph Hellwig
2022-06-03  6:55 ` [PATCH 02/11] scsi: Rename sd_pr_command Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-20  7:13   ` Christoph Hellwig
2022-06-20  7:13     ` [dm-devel] " Christoph Hellwig
2022-06-03  6:55 ` [PATCH 03/11] scsi: Move sd_pr_type to header to share Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-05  3:58   ` Bart Van Assche
2022-06-05  3:58     ` [dm-devel] " Bart Van Assche
2022-06-20  7:13   ` Christoph Hellwig
2022-06-20  7:13     ` [dm-devel] " Christoph Hellwig
2022-06-03  6:55 ` [PATCH 04/11] block: Add PR callouts for read keys and reservation Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-20  7:14   ` Christoph Hellwig
2022-06-20  7:14     ` [dm-devel] " Christoph Hellwig
2022-06-03  6:55 ` [PATCH 05/11] scsi: Add support for block PR read keys/reservation Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-03  6:55 ` [PATCH 06/11] dm: " Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-03  6:55 ` [PATCH 07/11] scsi: target: Allow backends to hook into PR handling Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-20  7:15   ` Christoph Hellwig
2022-06-20  7:15     ` [dm-devel] " Christoph Hellwig
2022-06-03  6:55 ` [PATCH 08/11] scsi: target: Add block PR support to iblock Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-20  7:18   ` Christoph Hellwig
2022-06-20  7:18     ` [dm-devel] " Christoph Hellwig
2022-06-03  6:55 ` [PATCH 09/11] block, nvme: Add error for reservation conflicts Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-03 19:45   ` Keith Busch
2022-06-03 19:45     ` [dm-devel] " Keith Busch
2022-06-03 23:08     ` Mike Christie
2022-06-03 23:08       ` [dm-devel] " Mike Christie
2022-06-04  7:38     ` Hannes Reinecke
2022-06-04  7:38       ` [dm-devel] " Hannes Reinecke
2022-06-04 17:13       ` michael.christie [this message]
2022-06-04 17:13         ` michael.christie
2022-06-05  9:42         ` Hannes Reinecke
2022-06-05  9:42           ` [dm-devel] " Hannes Reinecke
2022-06-20  7:23           ` Christoph Hellwig
2022-06-20  7:23             ` [dm-devel] " Christoph Hellwig
2022-06-05  4:00   ` Bart Van Assche
2022-06-05  4:00     ` Bart Van Assche
2022-06-03  6:55 ` [PATCH 10/11] scsi: Use BLK_STS_RSV_CONFLICT " Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-03  6:55 ` [PATCH 11/11] scsi: target: Handle BLK_STS_RSV_CONFLICT Mike Christie
2022-06-03  6:55   ` [dm-devel] " Mike Christie
2022-06-03 11:46 ` [PATCH 0/8] Use block pr_ops in LIO Christoph Hellwig
2022-06-03 11:46   ` [dm-devel] " Christoph Hellwig
2022-06-03 17:55   ` Mike Christie
2022-06-03 17:55     ` [dm-devel] " Mike Christie
2022-06-20  7:12     ` Christoph Hellwig
2022-06-20  7:12       ` [dm-devel] " Christoph Hellwig
2022-06-05  4:01 ` Bart Van Assche
2022-06-05  4:01   ` Bart Van Assche
2022-06-05 16:55   ` Mike Christie
2022-06-05 16:55     ` Mike Christie
2022-06-05 18:15     ` Bart Van Assche
2022-06-05 18:15       ` Bart Van Assche
2022-06-06 16:38       ` Mike Christie
2022-06-06 16:38         ` Mike Christie

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=6cc818cf-fac4-d485-ea9d-0b8597f24a33@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=snitzer@kernel.org \
    --cc=target-devel@vger.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 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.