From: Christoph Hellwig <hch@infradead.org>
To: Roger Willcocks <roger@filmlight.ltd.uk>
Cc: xfs@oss.sgi.com
Subject: xfstests testcase 111: Infinite xfs_bulkstat bad-inode loop case from Roger Willcocks
Date: Mon, 22 Dec 2008 11:58:50 -0500 [thread overview]
Message-ID: <20081222165848.GA17075@infradead.org> (raw)
Hi Roger,
I believe the xfstests case 111 is based on a report by you. Do you
remember what was going on there? From a look at the testcase it
overwrites an inode cluster and then tries to bulkstat them. This works
fine with a non-debug kernel, but due to debug kernels panicing it fails
there.
Do you remember what the testcase was looking for? I suspect we should
just not run it for debug kernels, but I'd like to know more about it
so we can add comments describing it.
Cheers,
Christoph
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2008-12-22 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 16:58 Christoph Hellwig [this message]
2008-12-22 20:28 ` xfstests testcase 111: Infinite xfs_bulkstat bad-inode loop casefrom Roger Willcocks Roger Willcocks
2008-12-22 20:50 ` Christoph Hellwig
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=20081222165848.GA17075@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