Greg KH wrote: > Ah, ok, that's a bit better, but then we need to figure out some way to > push "being used" down to a large majority of drivers, which we really > don't have.
And of course not just for storage; allow *all* the classes. I don't know how much effort it would be for storage - is a block device unaware that it has been mounted? I mean: does the kernel only keep a single link from the filesystem to the block device, and nothing the other way around? > Sounds like a lot of work for little gain :) Sure - is understood. It's probably particularly unimportant for storage vs. other classes, but it does seem ideal to defer access exclusion until the latest time possible. A very accurate model. I agree only achievable with a lot of work. //Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
