linux-ext4 - Re: fsck cannot fix block bitmap overlapping group descriptor

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: <20180806211650.GA19310@thunk.org>
Date:   Mon, 6 Aug 2018 17:16:50 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Benjamin Meier <maillists@...ienwohnung-altenbeken.de>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: fsck cannot fix block bitmap overlapping group descriptor

On Mon, Aug 06, 2018 at 07:02:31PM +0200, Benjamin Meier wrote:
> After switching to a newer kernel (4.9.110) I am not able to mount my
> ext4-filesystem read-write. fsck does not find any errors or anything to
> adjust. After spending hours of reading and learning I found the reason in
> these lines:

v4.9.110 doesn't have the code that you've referenced.  It looks like
it showed up in v4.9.112.

Unfortunately, the commit in question was introduced in v4.18-rc4, and
was buggy.  The fix[1] landed in v4.18-rc7, but it looks like that hasn't
been backported into the 4.9 series yet.

[1] Commit 44de022c4382: ext4: fix false negatives *and* false positives in ext4_check_descriptors()

... oh, I see.  It failed the automatic backport, so it has to be
manually backported to the 4.9 and 4.4 trees.  Someone thoughtful
backported it to the 4.14 tree, but not the others.

	      	     	  	    	- Ted