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

Message-ID: <20120313220000.GC11969@thunk.org>
Date:	Tue, 13 Mar 2012 18:00:01 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Frej Eriksson <frej.eriksson@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Fwd: ext4 extents.c bug

On Tue, Mar 13, 2012 at 09:14:18PM +0100, Frej Eriksson wrote:
> 
> 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?

If you run e2fsprogs with the patch applied, it will fix the file
system corruption that caused your kernel to BUG.  If the file system
corruption happens again (for whatever reason; kernel bug, hardware
problem, etc.) then the kernel will BUG instead of printing an
"EXT4-fs error" message and marking the file system as corrupted.

If you have your file system set to "tune2fs -e panic" there will be
no difference (since after the error message the kernel will be forced
to reboot so e2fsck can fix the problem).  But if you have your file
system set to "tune2fs -e continue" or "tune2fs -c read-only", where
you prefer that the file system be mounted read-only or just simply
continue after noting a file system corruption problem, and you want
that behavior, then you'd have to apply the kernel patch as well.
(You can see what the corrent behaviour on file systems errors by
looking at the output of "dumpe2fs -h /dev/sdXX | grep ^Errors".)

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/