From: Mark Tinguely <tinguely@sgi.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfs deadlock on buffer semaphore while reading directory
Date: Tue, 05 Feb 2013 17:59:31 -0600 [thread overview]
Message-ID: <51119CE3.6020409@sgi.com> (raw)
In-Reply-To: <20130202204601.GT30577@one.firstfloor.org>
On 02/02/13 14:46, Andi Kleen wrote:
>> That looks like a hang fixed by the series:
>>
>> http://oss.sgi.com/archives/xfs/2012-12/msg00071.html
>
> Great that it is already fixed. Thanks.
>
> Is the fix considered for stable?
>
> -Andi
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
Thanks for the reminder.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-05 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 19:20 xfs deadlock on buffer semaphore while reading directory Andi Kleen
2013-02-02 19:54 ` Mark Tinguely
2013-02-02 20:46 ` Andi Kleen
2013-02-05 23:59 ` Mark Tinguely [this message]
2013-02-03 6:35 ` Linda Walsh
2013-02-03 16:42 ` Stan Hoeppner
2013-02-06 0:44 ` Dave Chinner
2013-02-06 19:28 ` Linda Walsh
2013-02-10 2:04 ` Linda Walsh
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=51119CE3.6020409@sgi.com \
--to=tinguely@sgi.com \
--cc=andi@firstfloor.org \
--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