linux-ext4 - [PATCH 0/2] e2fprogs: block zero/discard cleanups

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <152399273813.4654.4884342501339028766.stgit@magnolia>
Date:   Tue, 17 Apr 2018 12:18:58 -0700
From:   "Darrick J. Wong" <darrick.wong@...cle.com>
To:     tytso@....edu, darrick.wong@...cle.com
Cc:     adilger@...ger.ca, linux-ext4@...r.kernel.org
Subject: [PATCH 0/2] e2fprogs: block zero/discard cleanups

Hi all,

Here's a couple of patches that make fallocate's ZERO_RANGE the
preferred implementation of unix_zeroout, and rearrange unix_zeroout and
unix_discard to try fallocate first always.  fallocate for block devices
has existed in the kernel for a few years now, and satisfies libext2fs'
requirement that reads following a zero/discard must return zeroes.  The
existing fallbacks for both functions are preserved.

Questions?  Comments?  This series targets e2fsprogs 1.45.

--D