From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <james.bottomley@hansenpartnership.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2/2] scsi: return BLK_STS_TRANSPORT for ALUA transitioning
Date: Tue, 24 May 2022 15:15:28 +0000 [thread overview]
Message-ID: <a3671fb2-fb43-2437-99fa-256aca1c76b2@nvidia.com> (raw)
In-Reply-To: <20220524055631.85480-3-hare@suse.de>
On 5/23/22 22:56, Hannes Reinecke wrote:
> When the 'ALUA state transitioning' sense code is returned we
> cannot use BLK_STS_AGAIN, as this has a very specific use-case.
> So return BLK_STS_TRANSPORT here.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
Do we need a fixes tag ? irrespective of that looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2022-05-24 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 5:56 [PATCH 0/2] block,scsi: BLK_STS_AGAIN clarification Hannes Reinecke
2022-05-24 5:56 ` [PATCH 1/2] block: document BLK_STS_AGAIN usage Hannes Reinecke
2022-05-24 8:36 ` Christoph Hellwig
2022-05-24 15:14 ` Chaitanya Kulkarni
2022-05-24 5:56 ` [PATCH 2/2] scsi: return BLK_STS_TRANSPORT for ALUA transitioning Hannes Reinecke
2022-05-24 15:15 ` Chaitanya Kulkarni [this message]
2022-06-02 2:39 ` Martin K. Petersen
2022-05-28 2:38 ` (subset) [PATCH 0/2] block,scsi: BLK_STS_AGAIN clarification Jens Axboe
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=a3671fb2-fb43-2437-99fa-256aca1c76b2@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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