From: Hannes Reinecke <hare@suse.de>
To: Niklas Cassel <niklas.cassel@wdc.com>, Jens Axboe <axboe@kernel.dk>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH v2 08/18] block: introduce BLK_STS_DURATION_LIMIT
Date: Fri, 13 Jan 2023 12:56:39 +0100 [thread overview]
Message-ID: <bd26aca3-2773-a080-ee87-0598fb6d47d1@suse.de> (raw)
In-Reply-To: <20230112140412.667308-9-niklas.cassel@wdc.com>
On 1/12/23 15:03, Niklas Cassel wrote:
> From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
>
> Introduce the new block IO status BLK_STS_DURATION_LIMIT for LLDDs to
> report command that failed due to a command duration limit being
> exceeded. This new status is mapped to the ETIME error code to allow
> users to differentiate "soft" duration limit failures from other more
> serious hardware related errors.
>
> Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
> Co-developed-by: Niklas Cassel <niklas.cassel@wdc.com>
> Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
> ---
> block/blk-core.c | 3 +++
> include/linux/blk_types.h | 6 ++++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/block/blk-core.c b/block/blk-core.c
> index b5098355d8b2..67b0b24aa171 100644
> --- a/block/blk-core.c
> +++ b/block/blk-core.c
> @@ -170,6 +170,9 @@ static const struct {
> [BLK_STS_ZONE_OPEN_RESOURCE] = { -ETOOMANYREFS, "open zones exceeded" },
> [BLK_STS_ZONE_ACTIVE_RESOURCE] = { -EOVERFLOW, "active zones exceeded" },
>
> + /* Command duration limit device-side timeout */
> + [BLK_STS_DURATION_LIMIT] = { -ETIME, "duration limit exceeded" },
> +
> /* everything else not covered above: */
> [BLK_STS_IOERR] = { -EIO, "I/O" },
> };
> diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
> index 99be590f952f..cde997590765 100644
> --- a/include/linux/blk_types.h
> +++ b/include/linux/blk_types.h
> @@ -166,6 +166,12 @@ typedef u16 blk_short_t;
> */
> #define BLK_STS_OFFLINE ((__force blk_status_t)17)
>
> +/*
> + * BLK_STS_DURATION_LIMIT is returned from the driver when the target device
> + * aborted the command because it exceeded one of its Command Duration Limits.
> + */
> +#define BLK_STS_DURATION_LIMIT ((__force blk_status_t)18)
> +
> /**
> * blk_path_error - returns true if error may be path related
> * @error: status the request was completed with
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
next prev parent reply other threads:[~2023-01-13 12:07 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 14:03 [PATCH v2 00/18] Add Command Duration Limits support Niklas Cassel
2023-01-12 14:03 ` [PATCH v2 01/18] ata: libata: allow ata_scsi_set_sense() to not set CHECK_CONDITION Niklas Cassel
2023-01-13 7:49 ` Hannes Reinecke
2023-01-17 6:06 ` Christoph Hellwig
2023-01-17 7:10 ` Damien Le Moal
2023-01-17 7:12 ` Christoph Hellwig
2023-01-17 7:15 ` Damien Le Moal
2023-01-17 7:23 ` Christoph Hellwig
2023-01-12 14:03 ` [PATCH v2 02/18] ata: libata: allow ata_eh_request_sense() " Niklas Cassel
2023-01-13 7:51 ` Hannes Reinecke
2023-01-17 6:08 ` Christoph Hellwig
2023-01-12 14:03 ` [PATCH v2 03/18] scsi: core: allow libata to complete successful commands via EH Niklas Cassel
2023-01-13 7:57 ` Hannes Reinecke
2023-01-16 12:43 ` Niklas Cassel
2023-01-17 11:44 ` Hannes Reinecke
2023-01-17 7:24 ` Christoph Hellwig
2023-01-12 14:03 ` [PATCH v2 04/18] scsi: rename and move get_scsi_ml_byte() Niklas Cassel
2023-01-13 7:58 ` Hannes Reinecke
2023-01-17 6:12 ` Christoph Hellwig
2023-01-12 14:03 ` [PATCH v2 05/18] scsi: support retrieving sub-pages of mode pages Niklas Cassel
2023-01-13 7:59 ` Hannes Reinecke
2023-01-17 6:13 ` Christoph Hellwig
2023-01-12 14:03 ` [PATCH v2 06/18] scsi: support service action in scsi_report_opcode() Niklas Cassel
2023-01-13 11:48 ` Hannes Reinecke
2023-01-17 6:13 ` Christoph Hellwig
2023-01-12 14:03 ` [PATCH v2 07/18] block: introduce duration-limits priority class Niklas Cassel
2023-01-13 11:55 ` Hannes Reinecke
2023-01-13 12:44 ` Damien Le Moal
2023-01-17 7:25 ` Christoph Hellwig
2023-01-17 8:06 ` Damien Le Moal
2023-01-17 8:13 ` Christoph Hellwig
2023-01-17 8:14 ` Damien Le Moal
2023-01-12 14:03 ` [PATCH v2 08/18] block: introduce BLK_STS_DURATION_LIMIT Niklas Cassel
2023-01-13 11:56 ` Hannes Reinecke [this message]
2023-01-17 7:26 ` Christoph Hellwig
2023-01-12 14:03 ` [PATCH v2 09/18] ata: libata: detect support for command duration limits Niklas Cassel
2023-01-13 11:59 ` Hannes Reinecke
2023-01-12 14:03 ` [PATCH v2 10/18] ata: libata-scsi: handle CDL bits in ata_scsiop_maint_in() Niklas Cassel
2023-01-12 14:04 ` [PATCH v2 11/18] ata: libata-scsi: add support for CDL pages mode sense Niklas Cassel
2023-01-12 14:04 ` [PATCH v2 12/18] ata: libata: add ATA feature control sub-page translation Niklas Cassel
2023-01-12 14:04 ` [PATCH v2 13/18] ata: libata: set read/write commands CDL index Niklas Cassel
2023-01-12 14:04 ` [PATCH v2 14/18] scsi: sd: detect support for command duration limits Niklas Cassel
2023-01-17 7:37 ` Christoph Hellwig
2023-01-17 8:00 ` Damien Le Moal
2023-01-12 14:04 ` [PATCH v2 15/18] scsi: sd: set read/write commands CDL index Niklas Cassel
2023-01-12 14:04 ` [PATCH v2 16/18] scsi: sd: handle read/write CDL timeout failures Niklas Cassel
2023-01-12 14:04 ` [PATCH v2 17/18] ata: libata: handle completion of CDL commands using policy 0xD Niklas Cassel
2023-01-12 14:04 ` [PATCH v2 18/18] Documentation: sysfs-block-device: document command duration limits Niklas Cassel
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=bd26aca3-2773-a080-ee87-0598fb6d47d1@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=niklas.cassel@wdc.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