On Fri, Jun 04, 2010 at 02:25:06PM -0400, Christoph Hellwig wrote: > Btw, simple reminder that all this has zero chance of going upstream > until someone addresses the issue of a proper API for locking down the > device mappings and getting the final block mapping in kernelspace. Do you have any more details on the issue? (Reference to a previous thread?) My (probably faulty) understanding of the the basic idea of the patches: a list of block signatures and a description of the desired topology is passed up to a userspace daemon, and the daemon cobbles together a device and passes down device major/minor numbers for the result. Are major/minor numbers the right way to hand off the device? (And what do you mean by "locking down the device mappings"? Is there a possibility the device can be destroyed while the kernel's using it?) --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
