https://bugzilla.kernel.org/show_bug.cgi?id=29162 Jeff Mahoney <jeffm@xxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweisbec@xxxxxxxxx, | |jeffm@xxxxxxxx --- Comment #8 from Jeff Mahoney <jeffm@xxxxxxxx> 2011-03-15 22:03:12 --- Bastien, are you using ACLs or security xattrs (e.g. selinux) on your file system? If you're not, I'll have to keep looking, but it seems as though Frederic's BKL replacement patches got the nested behavior of the BKL right but not the drop-over-schedule part completely right. The BKL can do nesting but drops the lock entirely over schedule. The reiserfs write lock can do nesting but only drops one reference to the lock over schedule. So if the lock is nested and a schedule occurs, the lock isn't truly dropped. The most obvious case of nesting the write lock like this is when using extended attributes since it will nest journal transactions. There are others, though. I'll work up a patch to test this theory and post it shortly. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
