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:     jack@suse.cz, osandov@fb.com, yukuai1@huaweicloud.com
Cc:     linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
        yi.zhang@huawei.com, yukuai3@huawei.com
In-Reply-To: <20220803121504.212071-1-yukuai1@huaweicloud.com>
References: <20220803121504.212071-1-yukuai1@huaweicloud.com>
Subject: Re: [PATCH] sbitmap: fix possible io hung due to lost wakeup
Message-Id: <166126186831.27028.2544657181662350295.b4-ty@kernel.dk>
Date:   Tue, 23 Aug 2022 07:37:48 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 3 Aug 2022 20:15:04 +0800, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@huawei.com>
> 
> There are two problems can lead to lost wakeup:
> 
> 1) invalid wakeup on the wrong waitqueue:
> 
> For example, 2 * wake_batch tags are put, while only wake_batch threads
> are woken:
> 
> [...]

Applied, thanks!

[1/1] sbitmap: fix possible io hung due to lost wakeup
      commit: 040b83fcecfb86f3225d3a5de7fd9b3fbccf83b4

Best regards,
-- 
Jens Axboe