linux-ext4 - Re: possible bug ?

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] [day] [month] [year] [list]

Message-ID: <20120919165039.GB21210@thunk.org>
Date:	Wed, 19 Sep 2012 12:50:39 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Adrian Sandu <dexter@...t3r01.tk>, linux-ext4@...r.kernel.org
Subject: Re: possible bug ?

On Wed, Sep 19, 2012 at 11:35:18AM -0500, Eric Sandeen wrote:
> 
> Actually argh, too many bugs.  ;)  I was thinking of 
> https://bugzilla.redhat.com/show_bug.cgi?id=857618
>
> (Lukas pointed at upstream commit 31d4f3a2f3c73f279ff96a7135d7202ef6833f12
> to avoid the BUG_ON but we still don't know the root cause I think).
> 
> Anyway, now I'm OT for this thread.

It is OT, so I've updated the RH bugzilla with my comments.

The one thing I would add is that we haven't been able to trigger this
via xfstests, so the workload needed trigger this must be fairly
unique/unusual.  (Which is why I suggested in the bugzilla update that
if someone sees this pattern of corruption, it would be very useful to
get the pathname of the inode in question, in the hopes that this
provides some hint as to what happened.)

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html