From: David Chinner <dgc@sgi.com>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [REVIEW] User-space support for bad_features2 patch
Date: Sat, 23 Feb 2008 16:00:11 +1100 [thread overview]
Message-ID: <20080223050011.GG155259@sgi.com> (raw)
In-Reply-To: <op.t6w1h5f53jf8g2@pc-bnaujok.melbourne.sgi.com>
[ please inline patches so they are easy to quote for review. ]
On Fri, Feb 22, 2008 at 06:52:43PM +1100, Barry Naujok wrote:
> The attached patch fixes mkfs.xfs writing the bad features2 in the first
> place (the change to xfs_sb.h does this).
>
> Next xfs_db support printing of this superblock field and xfs_check can
> report the bad_features2 field is set.
>
> xfs_repair can correct the error in the same fashion that David Chinner's
> mount code does it.
Actually, it doesn't:
/*
+ * Check bad_features2, if set and features2 is zero, copy
+ * bad_features2 to features2 and zero bad_features2.
+ */
+ if (sb->sb_bad_features2 != 0) {
+ if (sb->sb_features2 == 0)
+ sb->sb_features2 = sb->sb_bad_features2;
This simply copies the bad features over the features field if
the sb_features2 field is zero. This ignores the fact that we may
have set something into the sb_features2 field before detecting the
problem (e.g. attr2 can be turned on dynamically). The patch I posted
OR'd the two fields together to ensure no feature bits were lost.
This needs to be done here as well.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-02-23 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 7:52 [REVIEW] User-space support for bad_features2 patch Barry Naujok
2008-02-22 17:41 ` Eric Sandeen
2008-02-25 0:39 ` Barry Naujok
2008-02-25 8:42 ` Eric Sandeen
2008-02-25 9:55 ` Jan Derfinak
2008-02-23 5:00 ` David 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=20080223050011.GG155259@sgi.com \
--to=dgc@sgi.com \
--cc=bnaujok@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