On Sat, 2009-12-12 at 04:29 -0500, Jon Masters wrote: > FYI I am diagnosing an unlikely locking issue on a RHEL system right now > that triggers when you have a read-only filesystem and can't use file > locks. I know we ripped out a lot of that code since in upstream but I > might need to address this differently. I'll followup with my findings. I have written a sysV shared memory locking mechanism that using an shm segment in the case that the filesystem is mounted read-only. I'll finish the work on the RHEL bug and then forward port it, and post. We can probably re-introduce this because it works in a read-only context and can't be abused by a user to prevent module loading because the IPC shm segment is user-specific. Only downside is (optional, I guess) dependency on sysV shm. But I don't think we honestly have anyone wanting to use m-i-t on a system without such things compiled in. Jon. -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
