On May 7, 2009, at 6:55 PM, Eric Sandeen wrote:
Eric Sandeen wrote:
there are 2 subsequent unlocks for the same inode:
1:
xfs_iunlock: ip ca2304c0 ino 132 flags 0x5
...
2:
xfs_iunlock: ip ca230980 ino 131 flags 0x5
Ugh no, those are 2 different inodes.... I can read, really. :)
still,
looking into it.
I've been chasing this as well, and I found the double xfs iolock
unlock which is causing xfs_fsr deadlock itself. I have a fix tested.
The patch is coming.
Felix
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-
kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
