linux-kernel - [patch] RFC directio: partial writes support

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: <87iq9lxz3t.fsf@openvz.org>
Date:	Thu, 25 Feb 2010 15:45:58 +0300
From:	Dmitry Monakhov <dmonakhov@...nvz.org>
To:	linux-kernel@...r.kernel.org
CC:	linux-fsdevel@...r.kernel.org
Subject: [patch] RFC directio: partial writes support

Can someone please describe me why directio deny partial writes.
For example if someone try to write 100Mb but file system has less
data it return ENOSPC in the middle of block allocation.
All allocated blocks will be truncated (it may be 100Mb -4k) end
ENOSPC will be returned. As far as i remember direct_io always act
like this, but i never asked why?
Why do we have to give up all the progress we made?
In fact partial writes are possible in case of holes, when we 
fall back to buffered write. XFS implemented partial writes.

I've done trivial changes and it works like charm. 
Let's enable partial writes support and allow caller to define
this behavior.

View attachment "0001-direct_io-Allow-partial-writes.patch" of type "text/plain" (2190 bytes)