From: Daan De Meyer via B4 Relay <devnull+daan.amutable.com@kernel.org>
To: Jens Axboe <axboe@kernel.dk>,
Christian Brauner <brauner@kernel.org>,
Daan De Meyer <daan.j.demeyer@gmail.com>,
Josef Bacik <josef@toxicpanda.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
nbd@other.debian.org, Daan De Meyer <daan@amutable.com>,
stable@vger.kernel.org
Subject: [PATCH 0/2] loop, nbd: drop partitions left behind by the GD_NEED_PART_SCAN removal
Date: Thu, 06 Aug 2026 12:36:56 +0200 [thread overview]
Message-ID: <20260806-b4-loop-nbd-stale-partitions-v1-0-67bb75a8d7be@amutable.com> (raw)
Commit 267ec4d7223a ("loop: fix partition scan race between udev and
loop_reread_partitions()") stopped disk_force_media_change() from setting
GD_NEED_PART_SCAN. The caller audit in that commit only considered the bit
as a request to rescan partitions, but it did more than that:
bdev_disk_changed() drops every entry in disk->part_tbl before it consults
disk_has_partscan(), and only the re-adding half is gated on partition
scanning being enabled. The lazy scan on the next open was therefore also
the only thing removing partitions from a device that has partitions but
no partition scanning.
Loop devices without LO_FLAGS_PARTSCAN are exactly such devices, and they
are not unusual. bdev_add_partition() only rejects GENHD_FL_NO_PART disks,
so BLKPG_ADD_PARTITION works while GD_SUPPRESS_PART_SCAN is set, and
parted, libfdisk and systemd all fall back to BLKPG when BLKRRPART fails
with -EINVAL, which is what a loop device without LO_FLAGS_PARTSCAN
returns.
Commit c4f4c0fc551c ("loop: remove manually added partitions on detach")
fixed the detach path after this was reported as loop devices picking up
partition devices from a previously built image:
https://bugs.debian.org/1141434
These two patches fix the two remaining places that relied on the same
lazy cleanup, LOOP_CHANGE_FD and NBD_CLEAR_SOCK.
Both were tested with the blktests loop and nbd groups on 7.2-rc5. New
cases covering the two paths fail without these patches and pass with
them; they will be submitted to blktests separately.
Signed-off-by: Daan De Meyer <daan@amutable.com>
---
Daan De Meyer (2):
loop: drop stale partitions on LOOP_CHANGE_FD
nbd: drop stale partitions on NBD_CLEAR_SOCK
drivers/block/loop.c | 10 ++++++----
drivers/block/nbd.c | 7 +++++++
2 files changed, 13 insertions(+), 4 deletions(-)
---
base-commit: 248951ddc14de84de3910f9b13f51491a8cd91df
change-id: 20260806-b4-loop-nbd-stale-partitions-2d10ede71a2a
Best regards,
--
Daan De Meyer <daan@amutable.com>
next reply other threads:[~2026-08-06 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 10:36 Daan De Meyer via B4 Relay [this message]
2026-08-06 10:36 ` [PATCH 1/2] loop: drop stale partitions on LOOP_CHANGE_FD Daan De Meyer via B4 Relay
2026-08-06 10:36 ` [PATCH 2/2] nbd: drop stale partitions on NBD_CLEAR_SOCK Daan De Meyer via B4 Relay
2026-08-06 16:48 ` [PATCH 0/2] loop, nbd: drop partitions left behind by the GD_NEED_PART_SCAN removal Bart Van Assche
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=20260806-b4-loop-nbd-stale-partitions-v1-0-67bb75a8d7be@amutable.com \
--to=devnull+daan.amutable.com@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=daan.j.demeyer@gmail.com \
--cc=daan@amutable.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=stable@vger.kernel.org \
/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