From: Felix Blyakher <felixb@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Kernel Testers List <kernel-testers@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Beregalov <a.beregalov@gmail.com>,
xfs@oss.sgi.com
Subject: Re: 2.6.30-rc4: xfs_fsr hangs
Date: Thu, 7 May 2009 20:04:17 -0500 [thread overview]
Message-ID: <ABCCDF18-5100-4891-AF1C-BA9513C8A334@sgi.com> (raw)
In-Reply-To: <4A037503.1070904@sandeen.net>
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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-05-08 1:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 20:33 2.6.30-rc4: xfs_fsr hangs Alexander Beregalov
2009-05-02 10:14 ` Heinz Diehl
2009-05-02 18:35 ` Alexander Beregalov
2009-05-02 18:56 ` Eric Sandeen
2009-05-02 18:59 ` Alexander Beregalov
2009-05-02 20:14 ` Eric Sandeen
2009-05-03 1:47 ` Ed Tomlinson
2009-05-03 4:58 ` Eric Sandeen
2009-05-03 7:15 ` Alexander Beregalov
2009-05-03 14:30 ` Eric Sandeen
2009-05-03 20:33 ` Alexander Beregalov
2009-05-05 8:54 ` Alexander Beregalov
2009-05-07 23:33 ` Eric Sandeen
2009-05-07 23:55 ` Eric Sandeen
2009-05-08 1:04 ` Felix Blyakher [this message]
2009-05-08 1:09 ` Eric Sandeen
2009-05-08 1:17 ` Felix Blyakher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ABCCDF18-5100-4891-AF1C-BA9513C8A334@sgi.com \
--to=felixb@sgi.com \
--cc=a.beregalov@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox