linux-ext4 - [PATCH 0/4] ext4: Allow writeback IO without io

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-next>] [day] [month] [year] [list]

Message-Id: <20170510074147.26743-1-jack@suse.cz>
Date:   Wed, 10 May 2017 09:41:43 +0200
From:   Jan Kara <jack@...e.cz>
To:     Ted Tso <tytso@....edu>
Cc:     <linux-ext4@...r.kernel.org>, Jan Kara <jack@...e.cz>
Subject: [PATCH 0/4] ext4: Allow writeback IO without io_end

Hello,

this patch series allows ext4 to do page writeback without having io_end
allocated for the cases when block allocation is not required (it is the part
of my writepages improvements that didn't get merged in the first round). In
such cases io_end is not really necessary (it is really required only when
extent conversion has to happen after IO has finished) so just tweak the IO
completion code to allow IO submission without io_end allocated. It saves us
memory allocation on writeback path - it is not a big deal for performance but
it is nice in close-to-ENOMEM situations.

The patches have passed xfstests for ext4 and ext3 configurations,
specifically I have taken care to verify IO error handling still works.

								Honza