linux-kernel - Re: FAQ updated (was Re: XFS breakage...)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Jul 2006 09:11:21 -0700
From:	Chris Wedgwood <cw@...f.org>
To:	David Greaves <david@...eaves.com>
Cc:	Nathan Scott <nathans@....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 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.
-
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/