I can agree that some kind of limited sanity check might be a good idea
given that there might be a lot of broken partitions out there, and
putting a check in the kernel while reading in the partition is the
easiest way to make sure that the user gets warned.
However, a complicated locking scheme seems to me to be overkill. Next
thing you know, people will be asking for locking schemes for memory to
protect against the fumble-fingered administrator who types "mke2fs
/dev/mem" instead of "mke2fs /dev/ram". :-)
If the bug is in a broken version of fdisk, we should fix fdisk....
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu