Linux block layer
 help / color / mirror / Atom feed
From: Hongling Zeng <zhongling0719@126.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	 Ming Lei <tom.leiming@gmail.com>
Cc: Hongling Zeng <zenghongling@kylinos.cn>,
	axboe@kernel.dk,  ming.lei@canonical.com,
	linux-block@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block/loop: Fix NULL pointer dereference in lo_rw_aio()
Date: Wed, 20 May 2026 11:20:38 +0800	[thread overview]
Message-ID: <6A0D2886.1020707@126.com> (raw)
In-Reply-To: <8f5602c6-52c6-4c96-9c85-892160b1718b@I-love.SAKURA.ne.jp>

   Thanks, I'll review Tetsuo's analysis to better understand
   the full scope of the issue.

在 2026年05月19日 20:37, Tetsuo Handa 写道:
> On 2026/05/19 20:28, Ming Lei wrote:
>>> This means |__loop_clr_fd()|runs while I/O is still active.
>>> Regression introduced by:
>>> 6050fa4c84cc ("loop: don't hold lo_mutex during __loop_clr_fd()")
>> Why do you conclude it is caused by above commit?
> Some commit in the merge window for 7.1 broke the loop driver.
> Even synchronize_rcu() + drain_workqueue(lo->workqueue) is not sufficient.
> Please see a thread at https://lkml.kernel.org/r/d43125ff-cc66-49b7-b16d-1b2650c68c23@I-love.SAKURA.ne.jp .


      reply	other threads:[~2026-05-20  3:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  4:01 [PATCH] block/loop: Fix NULL pointer dereference in lo_rw_aio() Hongling Zeng
2026-05-19  4:42 ` Ming Lei
2026-05-19  6:06   ` Hongling Zeng
2026-05-19  8:33     ` Ming Lei
     [not found]       ` <6A0C29F6.5080704@126.com>
2026-05-19 11:28         ` Ming Lei
2026-05-19 12:37           ` Tetsuo Handa
2026-05-20  3:20             ` Hongling Zeng [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6A0D2886.1020707@126.com \
    --to=zhongling0719@126.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=tom.leiming@gmail.com \
    --cc=zenghongling@kylinos.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox