From: Christoph Hellwig <hch@infradead.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, Martijn Coenen <maco@android.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH v2] loop: LOOP_CONFIGURE: send uevents for partitions
Date: Wed, 15 Mar 2023 08:48:40 -0700 [thread overview]
Message-ID: <ZBHo2AXYM0iVkXvO@infradead.org> (raw)
In-Reply-To: <20230312191031.551204-1-hi@alyssa.is>
On Sun, Mar 12, 2023 at 07:10:31PM +0000, Alyssa Ross wrote:
> + * Now that we are done, reread the partitions with uevent
> + * re-enabled if appropriate to let userspace know about the
> + * changes.
> + */
> + dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), !partscan_uevent);
> + if (partscan)
> + loop_reread_partitions(lo);
> + dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 0);
What worries me here is that you move the partition re-read out of
the exclusive claim, which is another potentially user visible
change (and user visible behavior changes are a field of landmines
in loop as you have noticed).
But in the end we only need to suppress the events until Lo_Bound
is set. So something like the patch below that reduces the no even
critical section might do the job?
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 839373451c2b7d..9d61c027185141 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1010,9 +1010,6 @@ static int loop_configure(struct loop_device *lo, fmode_t mode,
/* This is safe, since we have a reference from open(). */
__module_get(THIS_MODULE);
- /* suppress uevents while reconfiguring the device */
- dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 1);
-
/*
* If we don't hold exclusive handle for the device, upgrade to it
* here to avoid changing device under exclusive owner.
@@ -1067,6 +1064,9 @@ static int loop_configure(struct loop_device *lo, fmode_t mode,
}
}
+ /* suppress uevents while reconfiguring the device */
+ dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 1);
+
disk_force_media_change(lo->lo_disk, DISK_EVENT_MEDIA_CHANGE);
set_disk_ro(lo->lo_disk, (lo->lo_flags & LO_FLAGS_READ_ONLY) != 0);
@@ -1109,17 +1109,17 @@ static int loop_configure(struct loop_device *lo, fmode_t mode,
if (partscan)
clear_bit(GD_SUPPRESS_PART_SCAN, &lo->lo_disk->state);
+ /* enable and uncork uevent now that we are done */
+ dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 0);
+
loop_global_unlock(lo, is_loop);
if (partscan)
loop_reread_partitions(lo);
+
if (!(mode & FMODE_EXCL))
bd_abort_claiming(bdev, loop_configure);
- error = 0;
-done:
- /* enable and uncork uevent now that we are done */
- dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 0);
- return error;
+ return 0;
out_unlock:
loop_global_unlock(lo, is_loop);
@@ -1130,7 +1130,7 @@ static int loop_configure(struct loop_device *lo, fmode_t mode,
fput(file);
/* This is safe: open() is still holding a reference. */
module_put(THIS_MODULE);
- goto done;
+ return error;
}
static void __loop_clr_fd(struct loop_device *lo, bool release)
next prev parent reply other threads:[~2023-03-15 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 19:10 [PATCH v2] loop: LOOP_CONFIGURE: send uevents for partitions Alyssa Ross
2023-03-15 15:48 ` Christoph Hellwig [this message]
2023-03-18 1:50 ` Alyssa Ross
2023-03-20 6:22 ` Christoph Hellwig
2023-03-20 10:20 ` Alyssa Ross
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=ZBHo2AXYM0iVkXvO@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=hi@alyssa.is \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.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