linux-ext4 - Re: [PATCH 2/5] ext4: fix block bitmap initialization under sparse

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: <20140512141618.GE31376@thunk.org>
Date:	Mon, 12 May 2014 10:16:18 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	"Darrick J. Wong" <darrick.wong@...cle.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 2/5] ext4: fix block bitmap initialization under
 sparse_super2

On Thu, May 01, 2014 at 04:17:34PM -0700, Darrick J. Wong wrote:
> The ext4_bg_has_super() function doesn't know about the new rules for
> where backup superblocks go on a sparse_super2 filesystem.  Therefore,
> block bitmap initialization doesn't know that it shouldn't reserve
> space for backups in groups that are never going to contain backups.
> The result of this is e2fsck complaining about the block bitmap being
> incorrect (fortunately not in a way that results in cross-linked
> files), so fix the whole thing.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@...cle.com>

Thanks, applied.

					- 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