On Mi, 23.06.21 16:01, Hannes Reinecke (hare@xxxxxxx) 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. Lennart -- Lennart Poettering, Berlin
