On Thu, Mar 18, 2010 at 05:13:22PM +0100, Kay Sievers wrote: > How about doing a two-stage instantiation instead of mangling events > to work around this setup model? Instead of creating the mentioned > event/sys inconsistencies, did you think about not registering the > "dead" blockdev until it is ready to be used as a blockdev? Like you > would allocate the dm instance in the kernel, but only register the > blockdev with the block subsystem when the device is resumed/the table > loaded. That way, only after the device is usable, it would get > registered and appear in /dev, /sys and proc. Still going around in circles, I'm afraid. That looked like even bigger block layer surgery last time we considered it. By all means, look at it yet again... We're creating trees of devices that reference each other (need to know minor numbers) and have constraints about which parts of the code may allocate new memory. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
