linux-ext4 - Re: Add ext4__allow_read-only_mounts_with_corrupted_block_group

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: <20080718125936.GG11221@mit.edu>
Date:	Fri, 18 Jul 2008 08:59:36 -0400
From:	Theodore Tso <tytso@....edu>
To:	Gary Hawco <ghawco@....net>
Cc:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Add
	ext4__allow_read-only_mounts_with_corrupted_block_group_checksums
	patch

On Tue, Jul 15, 2008 at 07:31:26PM +0000, Gary Hawco wrote:
> 
> Just recompiled 2.6.26 with the newest snapshot (15-July 2008/2310GMT).
> uninit_bg had been enabled.

I also just realized that while I had pushed the commit with the
patch, I had forgotten to include
ext4__allow_read-only_mounts_with_corrupted_block_group_checksums in
the series file.  Doh!

I just pushed out a series file which includes this, although that one
also is rebased against 2.6.26-git6 and removed all of the files from
the stable portion of the queue (since Linus has accepted them for the
merge window).

If you add 

   ext4__allow_read-only_mounts_with_corrupted_block_group_checksums

to the end of your series file, then the patch will actually be
applied.  :-)

Oops, and sorry for not noticing this sooner.

						- 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