From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] null_blk: Fix zone reset all tracing
Date: Wed, 4 Nov 2020 10:27:42 +0100 [thread overview]
Message-ID: <20201104092742.GA1669921@kroah.com> (raw)
In-Reply-To: <BL0PR04MB6514A24DB438A568A9C27CB7E7EF0@BL0PR04MB6514.namprd04.prod.outlook.com>
On Wed, Nov 04, 2020 at 09:21:27AM +0000, Damien Le Moal wrote:
> On 2020/11/04 18:14, Greg Kroah-Hartman wrote:
> > On Wed, Nov 04, 2020 at 10:10:15AM +0100, Greg Kroah-Hartman wrote:
> >> On Wed, Nov 04, 2020 at 02:29:14PM +0900, Damien Le Moal wrote:
> >>> commit f9c9104288da543cd64f186f9e2fba389f415630 upstream.
> >>>
> >>> 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>
> >>> ---
> >>> drivers/block/null_blk_zoned.c | 14 ++++++++------
> >>> 1 file changed, 8 insertions(+), 6 deletions(-)
> >>
> >> Now queued up, thanks.
> >
> > Wait, no, I'll delay this one until the next round as it's not fixing
> > something introduced in this -rc series.
>
> Yes, that problem is older.
> The lock fix I sent goes on top of this one though. I can send the backport for
> the lock fix without this patch applied. Is that OK ?
If the order of the patches is needed, then yes, I can take both, please
submit them as a patch series so that I know this is needed.
thanks,
greg k-h
next prev parent reply other threads:[~2020-11-04 9:26 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
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 [this message]
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=20201104092742.GA1669921@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--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).