Re: yet another approach to fix the loop lock order inversions v6
- To: Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>
- Cc: Jens Axboe <axboe@kernel.dk>, Josef Bacik <josef@toxicpanda.com>, Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>, "Darrick J . Wong" <djwong@kernel.org>, Ming Lei <ming.lei@redhat.com>, Matteo Croce <mcroce@microsoft.com>, linux-block@vger.kernel.org, nbd@other.debian.org
- Subject: Re: yet another approach to fix the loop lock order inversions v6
- From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
- Date: Tue, 5 Apr 2022 15:38:41 +0900
- Message-id: <[🔎] 2e052daf-214d-6921-1765-3b4974cea7cc@I-love.SAKURA.ne.jp>
- In-reply-to: <[🔎] 20220405062838.GA24373@lst.de>
- References: <20220330052917.2566582-1-hch@lst.de> <[🔎] 20220404074235.GA1046@lst.de> <[🔎] 499de381-c81e-4bd0-b5f7-1ee6be45821d@I-love.SAKURA.ne.jp> <[🔎] 20220405062838.GA24373@lst.de>
On 2022/04/05 15:28, Christoph Hellwig wrote:
> On Mon, Apr 04, 2022 at 06:39:31PM +0900, Tetsuo Handa wrote:
>> Two bugs which Jan has found in /bin/mount might not be yet fixed in
>> versions developers/users are using. Thus, let's wait for a while
>> before committing to linux.git.
>
> Jan, which loop bugs might be relevant here?
Since async __loop_clr_fd() was reverted, these bugs should
no longer be relevant. But different bugs might be found with
this series. Thus, let's stay careful for a while...
Reply to: