linux-kernel - Re: [2/3] 2.6.22-rc1: known regressions v2

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]

Message-ID: <464B9664.2040200@goop.org>
Date:	Wed, 16 May 2007 16:40:20 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	David Chinner <dgc@....com>
CC:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, xfs-masters@....sgi.com
Subject: Re: [2/3] 2.6.22-rc1: known regressions v2 - XFS

David Chinner wrote:
> Jeremy has tentatively indicated that the patch has fixed the problem.
> Have you seen any more problems since applying the patch, Jeremy?
>   

No, it continues to seem sound with casual use; I would have expected to
see the problem reoccur by now.  I'd like to rerun the full set of tests
I did before to be sure, but so far so good.  No other apparent
regressions either.

Also, the match between the observed symptoms and the bugfix is very
good, which adds confidence (ie, no element of "it works now but we
don't know why").  I guess the only remaining concern is whether there
are any other paths which fail to dirty the inode.

Did you manage to repro the problem?

    J
-
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/