[loopback device and bmap]
> > You could fall back to read/write in theory. There is an interesting project
> > for you 8)
>
> Really? Think about deadlocks. Both nbd and loop are _evil_. Mount
> sparse file over loopback, then write to both filessytems in heavy way
> to see why. THIS IS NOT EASY.
Time to embarrass myself once more on l-k ;) Intuition tells me that deadlocks
and races need to be thought about, but unfortunately I can't see what they
are.
How is writing to a filesystem on the loopbacked device simultaneously with
the hosting filesystem any different from writing to two files on the hosted
filesystem simultaneously?
Swapping, of course, is a different issue. Do we have any flags at the moment
which prevent people from trying to swap to inappropriate block devices (nbd,
certain raid levels with md, etc.)?
--
If you think the problem is bad now, just wait until we've solved it.
-- Arthur Kasspe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/