[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170050120665.99906.16634161281918179381.b4-ty@kernel.dk>
Date: Mon, 20 Nov 2023 10:26:46 -0700
From: Jens Axboe <axboe@...nel.dk>
To: bvanassche@....org, chengming.zhou@...ux.dev
Cc: kch@...dia.com, damien.lemoal@...nsource.wdc.com,
ming.lei@...hat.com, zhouchengming@...edance.com,
justinstitt@...gle.com, shinichiro.kawasaki@....com,
akinobu.mita@...il.com, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org,
syzbot+fcc47ba2476570cbbeb0@...kaller.appspotmail.com
Subject: Re: [PATCH] block/null_blk: Fix double blk_mq_start_request()
warning
On Mon, 20 Nov 2023 03:25:21 +0000, chengming.zhou@...ux.dev wrote:
> When CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, null_queue_rq()
> would return BLK_STS_RESOURCE or BLK_STS_DEV_RESOURCE for the request,
> which has been marked as MQ_RQ_IN_FLIGHT by blk_mq_start_request().
>
> Then null_queue_rqs() put these requests in the rqlist, return back to
> the block layer core, which would try to queue them individually again,
> so the warning in blk_mq_start_request() triggered.
>
> [...]
Applied, thanks!
[1/1] block/null_blk: Fix double blk_mq_start_request() warning
commit: 53f2bca2609237f910531f2c1a7779b16ce7952d
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists