stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] null_blk: Fix zone reset all tracing" failed to apply to 5.9-stable tree
Date: Tue, 3 Nov 2020 23:37:19 +0000	[thread overview]
Message-ID: <BL0PR04MB65144B8F266B12EED5DA6B5BE7110@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: 16044134474538@kroah.com

On 2020/11/03 23:23, gregkh@linuxfoundation.org wrote:
> 
> The patch below does not apply to the 5.9-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.

I will send a backported patch shortly. Thanks.

> 
> thanks,
> 
> greg k-h
> 
> ------------------ original commit in Linus's tree ------------------
> 
> From f9c9104288da543cd64f186f9e2fba389f415630 Mon Sep 17 00:00:00 2001
> From: Damien Le Moal <damien.lemoal@wdc.com>
> Date: Thu, 29 Oct 2020 20:04:59 +0900
> Subject: [PATCH] null_blk: Fix zone reset all tracing
> 
> In the cae of the REQ_OP_ZONE_RESET_ALL operation, the command sector is
> ignored and the operation is applied to all sequential zones. For these
> commands, tracing the effect of the command using the command sector to
> determine the target zone is thus incorrect.
> 
> Fix null_zone_mgmt() zone condition tracing in the case of
> REQ_OP_ZONE_RESET_ALL to apply tracing to all sequential zones that are
> not already empty.
> 
> Fixes: 766c3297d7e1 ("null_blk: add trace in null_blk_zoned.c")
> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> 
> diff --git a/drivers/block/null_blk_zoned.c b/drivers/block/null_blk_zoned.c
> index 98056c88926b..b637b16a5f54 100644
> --- a/drivers/block/null_blk_zoned.c
> +++ b/drivers/block/null_blk_zoned.c
> @@ -475,9 +475,14 @@ static blk_status_t null_zone_mgmt(struct nullb_cmd *cmd, enum req_opf op,
>  
>  	switch (op) {
>  	case REQ_OP_ZONE_RESET_ALL:
> -		for (i = dev->zone_nr_conv; i < dev->nr_zones; i++)
> -			null_reset_zone(dev, &dev->zones[i]);
> -		break;
> +		for (i = dev->zone_nr_conv; i < dev->nr_zones; i++) {
> +			zone = &dev->zones[i];
> +			if (zone->cond != BLK_ZONE_COND_EMPTY) {
> +				null_reset_zone(dev, zone);
> +				trace_nullb_zone_op(cmd, i, zone->cond);
> +			}
> +		}
> +		return BLK_STS_OK;
>  	case REQ_OP_ZONE_RESET:
>  		ret = null_reset_zone(dev, zone);
>  		break;
> 
> 


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2020-11-03 23:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 14:24 FAILED: patch "[PATCH] null_blk: Fix zone reset all tracing" failed to apply to 5.9-stable tree gregkh
2020-11-03 23:37 ` Damien Le Moal [this message]
2020-11-04  5:29 ` [PATCH] null_blk: Fix zone reset all tracing Damien Le Moal
2020-11-04  9:10   ` Greg Kroah-Hartman
2020-11-04  9:15     ` Greg Kroah-Hartman
2020-11-04  9:21       ` Damien Le Moal
2020-11-04  9:27         ` Greg Kroah-Hartman
2020-11-04  9:31           ` Damien Le Moal
2020-11-04  9:51             ` Greg Kroah-Hartman
2020-11-04  9:54               ` Damien Le Moal
2020-11-04 11:27               ` [PATCH 0/3] null_blk fixes for 5.9 stable Damien Le Moal
2020-11-04 11:27                 ` [PATCH 1/3] null_blk: synchronization fix for zoned device Damien Le Moal
2020-11-04 11:27                 ` [PATCH 2/3] null_blk: Fix zone reset all tracing Damien Le Moal
2020-11-04 11:27                 ` [PATCH 3/3] null_blk: Fix locking in zoned mode Damien Le Moal
2020-11-04 12:24                 ` [PATCH 0/3] null_blk fixes for 5.9 stable Greg Kroah-Hartman

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=BL0PR04MB65144B8F266B12EED5DA6B5BE7110@BL0PR04MB6514.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@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 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).