From: Christoph Hellwig <hch@infradead.org>
To: Roger Willcocks <roger@filmlight.ltd.uk>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfstests testcase 111: Infinite xfs_bulkstat bad-inode loop casefrom Roger Willcocks
Date: Mon, 22 Dec 2008 15:50:31 -0500 [thread overview]
Message-ID: <20081222205031.GB23453@infradead.org> (raw)
In-Reply-To: <C73606AC84514BE3B733F818ACCD281B@BODDINGTON>
On Mon, Dec 22, 2008 at 08:28:59PM -0000, Roger Willcocks wrote:
> Hi Christoph,
>
> here are the relevant extracts from our in-house bugzilla (bug 3675).
> Since the problem only occurs when the disk is corrupted, I don't see any
> problem with skipping the test on debug kernels.
Thanks a lot, that's some very helpful notes. I'll put a shortened
version of this into the testcase as a comment.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-22 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 16:58 xfstests testcase 111: Infinite xfs_bulkstat bad-inode loop case from Roger Willcocks Christoph Hellwig
2008-12-22 20:28 ` xfstests testcase 111: Infinite xfs_bulkstat bad-inode loop casefrom " Roger Willcocks
2008-12-22 20:50 ` Christoph Hellwig [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=20081222205031.GB23453@infradead.org \
--to=hch@infradead.org \
--cc=roger@filmlight.ltd.uk \
--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