public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Roel van Meer <rolek@bokxing.nl>
Cc: xfs@oss.sgi.com
Subject: Re: 2.6.32.11 hangs with xfstest 104
Date: Sat, 17 Apr 2010 09:47:24 +1000	[thread overview]
Message-ID: <20100416234724.GD2493@dastard> (raw)
In-Reply-To: <cone.1271414893.151380.55874.1001@bork.lsof.org>

On Fri, Apr 16, 2010 at 12:48:13PM +0200, Roel van Meer wrote:
> Hi list,
> 
> 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.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-04-16 23:45 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 [this message]
2010-04-19  9:08   ` Roel van Meer

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=20100416234724.GD2493@dastard \
    --to=david@fromorbit.com \
    --cc=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