Andrew Morton wrote:
Hrm... interesting but sounds like that could be sticky. For instance,
what if the user script that does the verifying happens to be ON the
volume to be verified?
Well that would be a bug. Solutions would be a) don't put the scripts on a
removable/power-downable device or b) use tmpfs.
I don't see how it could be a bug, just think of the root on usb case.
Keeping the program locked in ram would sidestep that issue, but tmpfs
is pagable right? Swap on usb?
Also, this user space program isn't going to be able to keep fully up to
date on what the disk looks like. Imagine a filesystem that keeps a
generation counter in the super block and increments it every time it
writes to the disk. The user space daemon might read that, then the fs
changes it, you suspend, and when you wake up, the daemon thinks the
media changed because it wasn't fully up to date.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
