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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 15 Sep 2014 17:44:41 -0400
From:	Milosz Tanski <>
To:	Christoph Hellwig <>
Cc:	Al Viro <>,
	LKML <>,
	"" <>,, Mel Gorman <>,
	Volker Lendecke <>,
	Tejun Heo <>, Jeff Moyer <>
Subject: Re: [PATCH 1/7] Prepare for adding a new readv/writev with user flags.

I'll redo with the flag inside of kiocb for the next submission.

On Mon, Sep 15, 2014 at 5:15 PM, Christoph Hellwig <> wrote:
> On Mon, Sep 15, 2014 at 09:28:28PM +0100, Al Viro wrote:
>> On Mon, Sep 15, 2014 at 04:20:17PM -0400, Milosz Tanski wrote:
>> > Plumbing the flags argument through the vfs code so they can be passed down to
>> > __generic_file_(read/write)_iter function that do the acctual work.
>> NAK.  Put these flags into iocb, it'll be less noisy that way.
> Fine with me.  My initial prototype had it in the iov_iter type field
> which is another possibility.
> But if we get rid of the explicit flags field and make it more invisible
> I'd really like to add a features field struct file_operations where
> instances can advertize that they support it (and other things like
> actual AIO support in the future) so that we won't have a situation
> like with AIO where we can submit I/O but it might actually still block
> anyway because lots of operations don't support it.

Milosz Tanski
16 East 34th Street, 15th floor
New York, NY 10016

p: 646-253-9055
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists