From: Hannes Reinecke <email@example.com> To: Lennart Poettering <firstname.lastname@example.org> Cc: Matteo Croce <email@example.com>, Christoph Hellwig <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Jens Axboe <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, Luca Boccassi <email@example.com>, Alexander Viro <firstname.lastname@example.org>, Damien Le Moal <email@example.com>, Tejun Heo <firstname.lastname@example.org>, Javier Gonz??lez <email@example.com>, Niklas Cassel <firstname.lastname@example.org>, Johannes Thumshirn <email@example.com>, Matthew Wilcox <firstname.lastname@example.org>, JeffleXu <email@example.com> Subject: Re: [PATCH v3 1/6] block: add disk sequence number Date: Wed, 23 Jun 2021 17:02:55 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <YNNBOyUiztf2wxDu@gardel-login> On 6/23/21 4:12 PM, Lennart Poettering wrote: > On Mi, 23.06.21 16:01, Hannes Reinecke (email@example.com) wrote: > >>> Thus: a global instead of local sequence number counter is absolutely >>> *key* for the problem this is supposed to solve >>> >> Well ... except that you'll need to keep track of the numbers (otherwise you >> wouldn't know if the numbers changed, right?). >> And if you keep track of the numbers you probably will have to implement an >> uevent listener to get the events in time. > > Hmm? This is backwards. The goal here is to be able to safely match up > uevents to specific uses of a block device, given that block device > names are agressively recycled. > > you imply it was easy to know which device use a uevent belongs > to. But that's the problem: it is not possible to do so safely. if i > see a uevent for a block device "loop0" I cannot tell if it was from > my own use of the device or for some previous user of it. > > And that's what we'd like to see fixed: i.e. we query the block device > for the seqeno now used and then we can use that to filter the uevents > and ignore the ones that do not carry the same sequence number as we > got assigned for our user. > It is notoriously tricky to monitor the intended use-case for kernel devices, precisely because we do _not_ attach any additional information to it. I have send a proposal for LSF to implement block-namespaces, the prime use-case of which is indeed attaching cgroup/namespace information to block devices such that we _can_ match (block) devices to specific contexts. Which I rather prefer than adding sequence numbers to block devices; incidentally you could solve the same problem by _not_ reusing numbers aggressively but rather allocate the next free one after the most recently allocated one. Will give you much the same thing without having to burden others with it. The better alternative here would be to extend the loop ioctl to pass in an UUID when allocating the device. That way you can easily figure out whether the loop device has been modified. But in the end, it's the loop driver and I'm not particular bothered with it. I am, though, if you need to touch all drivers just to support one particular use-case in one particular device driver. Incidentally, we don't have this problem in SCSI as we _can_ identify devices here. So in the end we couldn't care less on which /dev/sdX device it ends up. And I guess that's what we should attempt for loop devices, too. Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect firstname.lastname@example.org +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2021-06-23 15:02 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-23 10:58 [PATCH v3 0/6] block: add a sequence number to disks Matteo Croce 2021-06-23 10:58 ` [PATCH v3 1/6] block: add disk sequence number Matteo Croce 2021-06-23 11:48 ` Christoph Hellwig 2021-06-23 13:10 ` Matteo Croce 2021-06-23 13:51 ` Lennart Poettering 2021-06-23 14:01 ` Hannes Reinecke 2021-06-23 14:07 ` Luca Boccassi 2021-06-23 14:21 ` Hannes Reinecke 2021-06-23 14:34 ` Luca Boccassi 2021-06-23 14:55 ` Lennart Poettering 2021-06-23 14:12 ` Lennart Poettering 2021-06-23 15:02 ` Hannes Reinecke [this message] 2021-06-23 15:34 ` Luca Boccassi 2021-06-23 15:48 ` Lennart Poettering 2021-06-23 14:28 ` Christoph Hellwig 2021-06-23 10:58 ` [PATCH v3 2/6] block: add ioctl to read the " Matteo Croce 2021-06-23 10:58 ` [PATCH v3 3/6] block: refactor sysfs code Matteo Croce 2021-06-23 11:52 ` Christoph Hellwig 2021-06-23 19:03 ` Matteo Croce 2021-06-24 6:12 ` Christoph Hellwig 2021-06-23 10:58 ` [PATCH v3 4/6] block: export diskseq in sysfs Matteo Croce 2021-06-23 10:58 ` [PATCH v3 5/6] block: increment sequence number Matteo Croce 2021-06-23 10:58 ` [PATCH v3 6/6] loop: " Matteo Croce 2021-06-23 11:57 ` Christoph Hellwig 2021-06-23 13:13 ` Luca Boccassi 2021-06-23 14:25 ` Christoph Hellwig 2021-06-23 15:29 ` Lennart Poettering 2021-06-24 6:11 ` Christoph Hellwig 2021-06-23 12:03 ` [PATCH v3 0/6] block: add a sequence number to disks Hannes Reinecke 2021-06-23 12:46 ` Luca Boccassi 2021-06-23 14:07 ` Lennart Poettering
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v3 1/6] block: add disk sequence number' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).