Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8;
From:   Jens Axboe <axboe@kernel.dk>
To:     bvanassche@acm.org, chengming.zhou@linux.dev
Cc:     kch@nvidia.com, damien.lemoal@opensource.wdc.com,
        ming.lei@redhat.com, zhouchengming@bytedance.com,
        justinstitt@google.com, shinichiro.kawasaki@wdc.com,
        akinobu.mita@gmail.com, linux-block@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        syzbot+fcc47ba2476570cbbeb0@syzkaller.appspotmail.com
In-Reply-To: <20231120032521.1012037-1-chengming.zhou@linux.dev>
References: <20231120032521.1012037-1-chengming.zhou@linux.dev>
Subject: Re: [PATCH] block/null_blk: Fix double blk_mq_start_request()
 warning
Message-Id: <170050120665.99906.16634161281918179381.b4-ty@kernel.dk>
Date:   Mon, 20 Nov 2023 10:26:46 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk


On Mon, 20 Nov 2023 03:25:21 +0000, chengming.zhou@linux.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