From: Jens Axboe <axboe@kernel.dk>
To: Daan De Meyer <daan.j.demeyer@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Daan De Meyer <daan@amutable.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] loop: remove manually added partitions on detach
Date: Wed, 15 Jul 2026 16:34:35 -0600 [thread overview]
Message-ID: <178415487567.159585.4815884092425440929.b4-ty@b4> (raw)
In-Reply-To: <20260715-b4-loop-partition-cleanup-v1-1-b9f59910cd1e@amutable.com>
On Wed, 15 Jul 2026 21:39:57 +0200, Daan De Meyer wrote:
> Commit 267ec4d7223a ("loop: fix partition scan race between udev and
> loop_reread_partitions()") stopped disk_force_media_change() from
> setting GD_NEED_PART_SCAN because loop devices with LO_FLAGS_PARTSCAN
> rescan partitions explicitly. However, partitions can also be added
> manually with BLKPG while LO_FLAGS_PARTSCAN is clear.
>
> When such a loop device is detached, __loop_clr_fd() skips
> bdev_disk_changed(). Without GD_NEED_PART_SCAN, reopening the unbound
> device no longer performs the previous lazy cleanup, leaving dead
> partition devices behind. A subsequent LOOP_CONFIGURE can then fail its
> partition scan with -EBUSY, as seen in blktests loop/009 after loop/008.
>
> [...]
Applied, thanks!
[1/1] loop: remove manually added partitions on detach
commit: c4f4c0fc551cbcdccbbbc2d874d7d6440c7b4983
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-07-15 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 19:39 Daan De Meyer via B4 Relay
2026-07-15 22:34 ` Jens Axboe [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=178415487567.159585.4815884092425440929.b4-ty@b4 \
--to=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=daan.j.demeyer@gmail.com \
--cc=daan@amutable.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.sang@intel.com \
/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
all inboxes | Powered by JetHome®