> Except for the last the backtraces you're showing are for futex locks, > which are not used by the kernel, but some user process. So the locking > problem is somewhere in the user space setup (perhaps in qemu). > This would indicate your ext4 set up is not the same as LVM. Setup on the qemu/kvm is exactly the same (same test box, same command line arguments execept for the argument for the virtual machine disk which reference LVM volume or EXT4 based file) > > The later is the inode mutex which is needed for POSIX semantics > to get atomic writes. > Hmm, given that the user space thread is futexed in the 0xffffffff812132d8 : fsnotify+0x228/0x2f0 [kernel] isn't it really that the user space thread is blocked as a result of lock contention on the kernel inode mutex (ie: 0xffffffff811d5251 : new_sync_write+0x81/0xb0 [kernel]) and basically waits for the filesystem to be done with the write ? -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
