From: Bart Van Assche <bvanassche@acm.org>
To: daan@amutable.com, 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, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] loop, nbd: drop partitions left behind by the GD_NEED_PART_SCAN removal
Date: Thu, 6 Aug 2026 09:48:33 -0700 [thread overview]
Message-ID: <91e60d3d-4143-452a-a391-ca17df01e650@acm.org> (raw)
In-Reply-To: <20260806-b4-loop-nbd-stale-partitions-v1-0-67bb75a8d7be@amutable.com>
On 8/6/26 3:36 AM, Daan De Meyer via B4 Relay wrote:
> These two patches fix the two remaining places that relied on the same
> lazy cleanup, LOOP_CHANGE_FD and NBD_CLEAR_SOCK.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2026-08-06 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 10:36 [PATCH 0/2] loop, nbd: drop partitions left behind by the GD_NEED_PART_SCAN removal Daan De Meyer via B4 Relay
2026-08-06 10:36 ` Daan De Meyer
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 ` Daan De Meyer
2026-08-12 8:10 ` Shin'ichiro Kawasaki
2026-08-12 13:33 ` Christoph Hellwig
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 10:36 ` Daan De Meyer
2026-08-12 8:44 ` Shin'ichiro Kawasaki
2026-08-12 13:33 ` Christoph Hellwig
2026-08-06 16:48 ` Bart Van Assche [this message]
2026-08-12 9:51 ` [PATCH 0/2] loop, nbd: drop partitions left behind by the GD_NEED_PART_SCAN removal Christian Brauner
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=91e60d3d-4143-452a-a391-ca17df01e650@acm.org \
--to=bvanassche@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.