linux-kernel - Re: [PATCH 2/7] Define new syscalls readv2,preadv2,writev2,pwritev2

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

Message-ID: <20140917154327.GA12190@thunk.org>
Date:	Wed, 17 Sep 2014 11:43:27 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Milosz Tanski <milosz@...in.com>
Cc:	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	linux-fsdevel@...r.kernel.org, linux-aio@...ck.org,
	Mel Gorman <mgorman@...e.de>,
	Volker Lendecke <Volker.Lendecke@...net.de>,
	Tejun Heo <tj@...nel.org>, Jeff Moyer <jmoyer@...hat.com>
Subject: Re: [PATCH 2/7] Define new syscalls readv2,preadv2,writev2,pwritev2

On Mon, Sep 15, 2014 at 04:20:37PM -0400, Milosz Tanski wrote:
> New syscalls with an extra flag argument. For now all flags except for 0 are
> not supported.

This may fall in the category of bike-shedding, and so I apologize in
advance, but I wonder if we really need readv2 and writev2 as new
syscalls.  What if we just added preadv2 and pwritev2, and implemented
readv2 and writev2 as libc wrappers where which had the vector
allocated as an automatic stack variable?  Is the extra user memory
access really going to be that noticeable?

Cheers,

	       	      	       	       - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/