linux-ext4 - Re: [PATCH 0/10 v11] No wait AIO

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

Message-ID: <20170615145541.GA14028@infradead.org>
Date:   Thu, 15 Jun 2017 07:55:41 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Al Viro <viro@...IV.linux.org.uk>
Cc:     Christoph Hellwig <hch@...radead.org>,
        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 15, 2017 at 12:11:58PM +0100, Al Viro wrote:
> Which flags are you talking about?  aio ones?  AFAICS, it's the same
> kind of thing as "can we lseek?" or "can we read/pread?", etc.
> What would that field look like?  Note that some of those might depend
> upon the flags passed to open(), so shoving them into file_operations
> might mean splitting file_operations instances...  Details, please.

Yeah, I'll take my suggestion back.