[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060721081452.B1990742@wobbly.melbourne.sgi.com>
Date: Fri, 21 Jul 2006 08:14:52 +1000
From: Nathan Scott <nathans@....com>
To: Chris Wedgwood <cw@...f.org>
Cc: David Greaves <david@...eaves.com>,
Kasper Sandberg <lkml@...anurb.dk>,
Justin Piszcz <jpiszcz@...idpixels.com>,
Torsten Landschoff <torsten@...ian.org>,
linux-kernel@...r.kernel.org, xfs@....sgi.com, ml@...og.se,
radsaq@...il.com
Subject: Re: FAQ updated (was Re: XFS breakage...)
On Thu, Jul 20, 2006 at 09:11:21AM -0700, Chris Wedgwood wrote:
> On Thu, Jul 20, 2006 at 02:28:32PM +0100, David Greaves wrote:
>
> > Does this problem exist in 2.16.6.x??
>
> The change was merged after 2.6.16.x was branched, I was mistaken
> in how long I thought the bug has been about.
>
> > I hope so because I assumed there simply wasn't a patch for 2.6.16 and
> > applied this 'best guess' to my servers and rebooted/remounted successfully.
>
> Doing the correct change to 2.6.16.x won't hurt, but it's not
> necessary.
Yep. As Chris said, 2.6.17 is the only affected kernel. I've
fixed up the whacky html formatting and my merge error (thanks
to all for reporting those) so its a bit more readable now.
cheers.
--
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists