linux-kernel - Re: Fwd: ext4 extents.c 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACbLGLLLtD8TJd-VvdkQYo48nT5NFE8bmH8aHtwy6-hoCbqL9g@mail.gmail.com>
Date:	Tue, 13 Mar 2012 21:14:18 +0100
From:	Frej Eriksson <frej.eriksson@...il.com>
To:	"Ted Ts'o" <tytso@....edu>,
	Frej Eriksson <frej.eriksson@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Fwd: ext4 extents.c bug

Hi,

Thank you for your the information! If i get you correct does it mean
that you need to have an updated version of both the kernel and
e2fsprogs in order to have the issue fixed? Or is it enough to run
e2fsprogs with the patch applied?

Best regards,
Frej Eriksson

On Tue, Mar 13, 2012 at 8:57 PM, Ted Ts'o <tytso@....edu> wrote:
> On Tue, Mar 13, 2012 at 08:39:56PM +0100, Frej Eriksson wrote:
>> [  950.128885] ------------[ cut here ]------------
>> [  950.128893] kernel BUG at /build/buildd/linux-2.6.35/fs/ext4/extents.c:1971!
>
> Your file system is corrupted, and there are two bugs.  (1) e2fsck
> wasn't detecting this form of file system corruption (a zero-length
> extent entry), and (2) the kernel was not noticing until an assertion
> check using BUG_ON, instead of flagging this as a file systme error.
>
> The fixes for both of these problems, in the kernel and in e2fsprogs,
> are here:
>
>    http://article.gmane.org/gmane.comp.file-systems.ext4/31359
>    http://article.gmane.org/gmane.comp.file-systems.ext4/31360
>
> Best regards,
>
>                                                - Ted
--
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/