From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: jack@suse.cz
Subject: [PATCH 0/3] xfs: buffer types need to be set
Date: Wed, 21 Jan 2015 11:39:37 +1100 [thread overview]
Message-ID: <1421800780-26008-1-git-send-email-david@fromorbit.com> (raw)
Hi Jan,
These three patches detect and fix the issues you reported with log
recovery finding buffers with a format type of zero. The type of
zero (XFS_BLFT_UNKNOWN_BUF) is only valid for buffers that have
been cancelled (i.e. invalidated or marked stale as they have been
freed), so the series adds asserts to ensure these conditions are
met during transaction commit. Hence we shouldn't ever get new code
that fails to set the buffer type getting through testing.
The last two patches fix the cases that running xfstests uncovered
where we don't set the buffer type appropriately. There may be more,
but doing this much made my head hurt and xfstests is clean, so it's
as much as I'm going to do right now. Can you test it and see if it
runs clean (with CONFIG_XFS_WARN=y or CONFIG_XFS_DEBUG=y) on your
test setup?
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-01-21 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 0:39 Dave Chinner [this message]
2015-01-21 0:39 ` [PATCH 1/3] xfs: ensure buffer types are set correctly Dave Chinner
2015-01-21 22:05 ` Brian Foster
2015-01-21 0:39 ` [PATCH 2/3] xfs: inode unlink does not set AGI buffer type Dave Chinner
2015-01-21 22:05 ` Brian Foster
2015-01-21 0:39 ` [PATCH 3/3] xfs: set buf types when converting extent formats Dave Chinner
2015-01-21 22:06 ` Brian Foster
2015-01-21 2:34 ` [PATCH 4/3] xfs: set superblock buffer type correctly Dave Chinner
2015-01-21 22:06 ` Brian Foster
2015-01-21 16:07 ` [PATCH 0/3] xfs: buffer types need to be set Jan Kara
2015-01-21 17:11 ` Jan Kara
2015-01-21 21:12 ` Dave Chinner
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=1421800780-26008-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=jack@suse.cz \
--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