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
| ||
|
Message-ID: <20170610053441.GD6365@ZenIV.linux.org.uk> Date: Sat, 10 Jun 2017 06:34:41 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: Christoph Hellwig <hch@...radead.org> Cc: Goldwyn Rodrigues <rgoldwyn@...e.de>, akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org, jack@...e.com, linux-block@...r.kernel.org, linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org, axboe@...nel.dk, linux-api@...r.kernel.org, adam.manzanares@....com Subject: Re: [PATCH 0/10 v11] No wait AIO On Thu, Jun 08, 2017 at 12:39:10AM -0700, Christoph Hellwig wrote: > As already indicated this whole series looks fine to me. > > Al: are you going to pick this up? Or Andrew? The main issue here is "let's bail out from ->write_iter() instances" patch. It very obviously has holes in coverage. Could we have FMODE_AIO_NOWAIT and make those who claim to support it set that in ->open()? And make aio check that and bail out if asked for nowait on a file without that flag...
Powered by blists - more mailing lists