Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jens Axboe <axboe@kernel.dk>
To:     yukuai1@huaweicloud.com, osandov@fb.com, ming.lei@redhat.com
Cc:     linux-block@vger.kernel.org, yukuai3@huawei.com,
        yi.zhang@huawei.com, linux-kernel@vger.kernel.org
In-Reply-To: <20220726122224.1790882-1-yukuai1@huaweicloud.com>
References: <20220726122224.1790882-1-yukuai1@huaweicloud.com>
Subject: Re: [PATCH v3] blk-mq: fix io hung due to missing commit_rqs
Message-Id: <166094258954.37536.4791587641314567827.b4-ty@kernel.dk>
Date:   Fri, 19 Aug 2022 20:56:29 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 26 Jul 2022 20:22:24 +0800, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@huawei.com>
> 
> Currently, in virtio_scsi, if 'bd->last' is not set to true while
> dispatching request, such io will stay in driver's queue, and driver
> will wait for block layer to dispatch more rqs. However, if block
> layer failed to dispatch more rq, it should trigger commit_rqs to
> inform driver.
> 
> [...]

Applied, thanks!

[1/1] blk-mq: fix io hung due to missing commit_rqs
      (no commit info)

Best regards,
-- 
Jens Axboe