From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7?
Date: Mon, 24 Jul 2006 12:40:47 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607241239460.10990@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0607241224010.10896@p34.internal.lan>
On Mon, 24 Jul 2006, Justin Piszcz wrote:
> Beginning at 2.6.17 to 2.6.17.6, there is a serious XFS bug that results in
> filesystem corruption, there was a 1 line bugfix patch that was released
> recently and I was wondering when 2.6.17.7 would be released with that patch?
> It affected ALL my Linux machines (x86) running XFS and many people on the
> XFS mailing list who upgraded to 2.6.17. I understand when there is a root
> exploit or DoS bug, the kernel is naturally patched by the -stable team and a
> new version is released immediately. Does filesystem corruption not
> constitute an immediate new -stable release of the kernel?
>
>
>
This fix was available as of 2.6.17.2, but not currently in 2.6.17.6...
http://marc.theaimsgroup.com/?l=linux-kernel&m=115315508506996&w=2
I am running all of my machines with this patch and rebooted a couple of
them with KNOPPIX and checked the FS, it seems to be OK now.
Justin.
next prev parent reply other threads:[~2006-07-24 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 16:29 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7? Justin Piszcz
2006-07-24 16:40 ` Justin Piszcz [this message]
2006-07-24 22:22 ` Daniel Drake
2006-07-24 22:46 ` Nathan Scott
2006-07-25 21:07 ` Matthias Andree
2006-07-25 21:09 ` Matthias Andree
2006-07-28 23:26 ` [stable] " Greg KH
2006-07-28 23:55 ` Dave Jones
2006-07-29 0:27 ` Greg KH
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=Pine.LNX.4.64.0607241239460.10990@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).