| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.6.30-rc4: xfs_fsr hangs |
| From: | Felix Blyakher <felixb@xxxxxxx> |
| Date: | Thu, 7 May 2009 20:04:17 -0500 |
| Cc: | Alexander Beregalov <a.beregalov@xxxxxxxxx>, Kernel Testers List <kernel-testers@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <4A037503.1070904@xxxxxxxxxxx> |
| References: | <a4423d670905011333s664115bdh1d72392897567c1d@xxxxxxxxxxxxxx> <4A036FBC.9020201@xxxxxxxxxxx> <4A037503.1070904@xxxxxxxxxxx> |
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 0x5Ugh 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" inthe 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/ |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 03/17] xfs: cleanup handling in xfs_swap_extents, Eric Sandeen |
|---|---|
| Next by Date: | Re: 2.6.30-rc4: xfs_fsr hangs, Eric Sandeen |
| Previous by Thread: | Re: 2.6.30-rc4: xfs_fsr hangs, Eric Sandeen |
| Next by Thread: | Re: 2.6.30-rc4: xfs_fsr hangs, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |