linux-ext4 - Re: [PATCH] ext4: use s_extent_max_zeroout

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]

Date:	Tue, 12 Mar 2013 12:45:11 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Lukas Czerner <lczerner@...hat.com>
Cc:	linux-ext4@...r.kernel.org, wenqing.lz@...bao.com
Subject: Re: [PATCH] ext4: use s_extent_max_zeroout_kb value as number of kb

Thanks, applied.

I'm on the fence about whether to submit this after -rc2 or not.
This appears to make potential bug much rarer, and it's a trivial
patch to backport, but it does make rather large changes in how we
handle fragmented filesystem.  (For the better, but it's a large
change, and it is getting rather late in the season.)

I'm going to include in the dev branch for now, and give it all a good
instensive testing, but there may be some patches in dev that may get
deferred to the next merge window before I send a pull request to
Linus (probably during the coming weekend).

Folks should feel free to propose patches they think should wait for
the next merge window.

					- 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