public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [REVIEW #3] bad_features2 support in user-space
Date: Fri, 29 Feb 2008 16:33:58 +1100	[thread overview]
Message-ID: <1204263238.13569.122.camel@edge.scott.net.au> (raw)
In-Reply-To: <op.t69rt3bp3jf8g2@pc-bnaujok.melbourne.sgi.com>

On Fri, 2008-02-29 at 15:52 +1100, Barry Naujok wrote:
> Ok, xfs_repair will leave bad_features2 in place just in case it is
> being run with an older kernel that expects features2 in the bad
> location. But, it will make sure the correct and bad features2 are
> consistent if bad_features2 in non-zero.
> 
> If bad_features2 is zero, it is left alone (eg. new mkfs or new
> kernel with fixes it during mount time).
> 
> This seems to be the best solution to the problem.
> 

*nod* - looks good to me...

> +	if (sb->sb_bad_features2 != 0 &&
> +			sb->sb_bad_features2 != sb->sb_features2) {
> +		sb->sb_features2 |= sb->sb_bad_features2;
> +		sb->sb_bad_features2 = sb->sb_features2;
> +		primary_sb_modified = 1;

No endian issues here are there?  It looks OK, but you tested it right?
(looked at what a little endian system writes ondisk?)

cheers.

-- 
Nathan

  reply	other threads:[~2008-02-29  5:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29  4:52 [REVIEW #3] bad_features2 support in user-space Barry Naujok
2008-02-29  5:33 ` Nathan Scott [this message]
2008-02-29  5:44 ` Eric Sandeen
2008-02-29  6:11   ` Josef 'Jeff' Sipek

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=1204263238.13569.122.camel@edge.scott.net.au \
    --to=nscott@aconex.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