From: Roel van Meer <rolek@bokxing.nl>
To: xfs@oss.sgi.com
Subject: Re: 2.6.32.11 hangs with xfstest 104
Date: Mon, 19 Apr 2010 11:08:33 +0200 [thread overview]
Message-ID: <cone.1271668113.965996.76612.1001@bork.lsof.org> (raw)
In-Reply-To: 20100416234724.GD2493@dastard
Dave Chinner writes:
>> I've been running xfstests on a slackware linux server with kernel
>> 2.6.32.11.
>> I've noticed that xfstest # 104 reliably hangs the kernel. Attached
>> are two call traces.
>
> Yes, it does, and has done since test 104 was written to exercise a
> growfs deadlock years ago. I re-enabled it in the auto group because
> it's been fixed it and those fixes are now in the 2.6.34-rc tree.
Aha, thanks. I can confirm that I did see the problem with 2.6.33.2 but that
I cannot reproduce it with 2.6.34-rc4, so everything seems to be like it
should be.
Thanks again,
roel
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-04-19 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 10:48 2.6.32.11 hangs with xfstest 104 Roel van Meer
2010-04-16 23:47 ` Dave Chinner
2010-04-19 9:08 ` Roel van Meer [this message]
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=cone.1271668113.965996.76612.1001@bork.lsof.org \
--to=rolek@bokxing.nl \
--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