From: Christoph Hellwig <hch@infradead.org>
To: Ben Myers <bpm@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [BUG] assert in xfs_imap_to_bp, line 185
Date: Tue, 8 Nov 2011 12:06:07 -0500 [thread overview]
Message-ID: <20111108170606.GA17457@infradead.org> (raw)
In-Reply-To: <20111108163932.GA22095@sgi.com>
On Tue, Nov 08, 2011 at 10:39:32AM -0600, Ben Myers wrote:
> Hi XFS Folks,
>
> I am able to hit this assert consistently when running test 111 on recent
> (commit 9e4c109a) oss xfs bits:
That's expected - the test must only be run on non-debug kernels. It
corrupt the inode, and then we read it. A normal kernel shouldn't
panic, but for the debug kernel we settled on an assert for it.
I'm not sure it's a smart idea, and WANT_CORRUPTED_GOTO might be
better in the end.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-08 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 16:39 [BUG] assert in xfs_imap_to_bp, line 185 Ben Myers
2011-11-08 17:06 ` Christoph Hellwig [this message]
2011-11-08 17:19 ` Ben Myers
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=20111108170606.GA17457@infradead.org \
--to=hch@infradead.org \
--cc=bpm@sgi.com \
--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