[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1687461.6WkTYu5mUM@natalenko.name>
Date: Fri, 16 Jul 2021 14:56:22 +0200
From: Oleksandr Natalenko <oleksandr@...alenko.name>
To: Ming Lei <ming.lei@...hat.com>
Cc: linux-kernel@...r.kernel.org, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
linux-nvme@...ts.infradead.org,
David Jeffery <djeffery@...hat.com>,
Laurence Oberman <loberman@...hat.com>,
Paolo Valente <paolo.valente@...aro.org>,
Jan Kara <jack@...e.cz>, Sasha Levin <sashal@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Keith Busch <kbusch@...nel.org>
Subject: Re: New warning in nvme_setup_discard
On pátek 16. července 2021 12:41:52 CEST Ming Lei wrote:
> > Do I understand correctly that this will be something like:
> >
> > Fixes: 2705dfb209 ("block: fix discard request merge")
> >
> > ?
> >
> > Because as the bisection progresses, I've bumped into this commit only.
> > Without it the issue is not reproducible, at least so far.
>
> It could be.
>
> So can you just test v5.14-rc1?
Doing it right now, but I've got another issue. Why BFQ is not listed here:
```
/sys/class/block/nvme0n1/queue/scheduler:[mq-deadline] kyber none
/sys/class/block/nvme1n1/queue/scheduler:[mq-deadline] kyber none
```
?
It is a built-in, FWIW:
```
$ modinfo bfq
name: bfq
filename: (builtin)
description: MQ Budget Fair Queueing I/O Scheduler
license: GPL
file: block/bfq
author: Paolo Valente
alias: bfq-iosched
```
So far the issue is not reproducible with your patch + 5.13.2 as well as 5.14-
rc1 (but I don't have BFQ either with v5.14-rc1).
--
Oleksandr Natalenko (post-factum)
Powered by blists - more mailing lists