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
| ||
|
Date: Wed, 1 Mar 2017 07:56:34 -0800 From: Christoph Hellwig <hch@...radead.org> To: Goldwyn Rodrigues <rgoldwyn@...e.de> Cc: jack@...e.com, hch@...radead.org, linux-fsdevel@...r.kernel.org, linux-block@...r.kernel.org, linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org, Goldwyn Rodrigues <rgoldwyn@...e.com> Subject: Re: [PATCH 1/8] nowait aio: Introduce IOCB_FLAG_NOWAIT On Wed, Mar 01, 2017 at 07:36:48AM -0800, Christoph Hellwig wrote: > Given that we aren't validating aio_flags in older kernels we can't > just add this flag as it will be a no-op in older kernels. I think > we will have to add IOCB_CMD_PREADV2/IOCB_CMD_WRITEV2 opcodes that > properly validate all reserved fields or flags first. > > Once we do that I'd really prefer to use the same flags values > as preadv2/pwritev2 so that we'll only need one set of flags over > sync/async read/write ops. I just took another look and we do verify that aio_reserved1/aio_reserved2 must be zero. So I think we can just stick RWF_* into aio_reserved1 and fix that problem that way.
Powered by blists - more mailing lists