From: "Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Barry Naujok <bnaujok@sgi.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [REVIEW #3] bad_features2 support in user-space
Date: Fri, 29 Feb 2008 01:11:18 -0500 [thread overview]
Message-ID: <20080229061118.GA22067@josefsipek.net> (raw)
In-Reply-To: <47C79BB8.4010005@sandeen.net>
On Thu, Feb 28, 2008 at 11:44:24PM -0600, Eric Sandeen wrote:
> 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.
>
> Will look at details later, but I agree w/ the general direction... I
> think maybe the kernel should go this way too? (i.e. kernel maybe
> shouldn't be zeroing features2 either...
I think so.
> but this is probably more important for userspace than kernelspace; how
> often do you revert to an older kernel...)
All you need is another subsystem in Linux to be broken (*cough*ACPI*cough*)
and you'll want to go back to your previous kernel.
Josef 'Jeff' Sipek.
--
A computer without Microsoft is like chocolate cake without mustard.
prev parent reply other threads:[~2008-02-29 6:11 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
2008-02-29 5:44 ` Eric Sandeen
2008-02-29 6:11 ` Josef 'Jeff' Sipek [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=20080229061118.GA22067@josefsipek.net \
--to=jeffpc@josefsipek.net \
--cc=bnaujok@sgi.com \
--cc=sandeen@sandeen.net \
--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