From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/9] Log and transaction cleanups, factoring and bug fixes
Date: Tue, 9 Mar 2010 22:48:18 +1100 [thread overview]
Message-ID: <20100309114818.GN28189@discord.disaster> (raw)
In-Reply-To: <20100309113919.GA5479@infradead.org>
On Tue, Mar 09, 2010 at 06:39:19AM -0500, Christoph Hellwig wrote:
> With the whole series (and my posted cleanups) applied I get the
> following XFSQA 113 failure (and a similar one before):
>
> [ 2064.763171] Assertion failed: xfs_lic_are_all_free(licp), file: fs/xfs/xfs_trans.c, line: 1432
Yeah, that's a bogus assert. I found it yesterday on test 113 ;)
The issue is that test 113 is the first QA test that is
semi-reliably creating a transaction with more than one chunk of log
item descriptors. The original assert was:
ASSERT(!xfs_lic_are_all_free(licp));
before it called xfs_trans_chunk_committed() and ran the commit
processing on all the items in the chunk. It then freed the chunk.
This makes sense - there should be items in the chunk being freed.
I made the bogus assumption when cleaning up the code that after
committed processing on all the items that all the items in the
chunk would be marked as freed. However, nothing cleans up the log
item descriptors in the committed item processing, so the items in
the chunk are all still marked as used.
The fix is to either remove the assert or invert the condition....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-03-09 11:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 1:51 [PATCH 0/9] Log and transaction cleanups, factoring and bug fixes Dave Chinner
2010-03-06 1:51 ` [PATCH 1/9] xfs: factor log item initialisation Dave Chinner
2010-03-06 10:51 ` Christoph Hellwig
2010-03-06 1:51 ` [PATCH 2/9] xfs: Add inode pin counts to traces Dave Chinner
2010-03-06 10:51 ` Christoph Hellwig
2010-03-06 1:51 ` [PATCH 3/9] xfs: remove stale parameter from ->iop_unpin method Dave Chinner
2010-03-06 10:55 ` Christoph Hellwig
2010-03-06 1:51 ` [PATCH 4/9] xfs: fix reservation release commit flag in xfs_bmap_add_attrfork() Dave Chinner
2010-03-06 10:52 ` Christoph Hellwig
2010-03-06 1:51 ` [PATCH 5/9] xfs: split out iclog writing from xfs_trans_commit() Dave Chinner
2010-03-06 11:08 ` Christoph Hellwig
2010-03-06 11:57 ` Dave Chinner
2010-03-06 1:51 ` [PATCH 6/9] xfs: update and factor xfs_trans_committed() Dave Chinner
2010-03-06 11:24 ` Christoph Hellwig
2010-03-06 12:01 ` Dave Chinner
2010-03-06 1:51 ` [PATCH 7/9] xfs: log ticket reservation underestimates the number of iclogs Dave Chinner
2010-03-15 2:13 ` Dave Chinner
2010-03-06 1:51 ` [PATCH 8/9] xfs: introduce new internal log vector structure Dave Chinner
2010-03-06 11:31 ` Christoph Hellwig
2010-03-06 12:06 ` Dave Chinner
2010-03-06 15:46 ` Christoph Hellwig
2010-03-08 1:16 ` Dave Chinner
2010-03-06 1:51 ` [PATCH 9/9] xfs: factor xlog_write and make use of new " Dave Chinner
2010-03-06 15:48 ` Christoph Hellwig
2010-03-06 10:56 ` [PATCH 0/9] Log and transaction cleanups, factoring and bug fixes Christoph Hellwig
2010-03-09 11:39 ` Christoph Hellwig
2010-03-09 11:48 ` Dave Chinner [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=20100309114818.GN28189@discord.disaster \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--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