linux-kernel - Vectored syscalls Was: [PATCH 0/3] readfile(2): a new syscall to make open/read/close faster

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

Message-Id: <3ADE6606-6572-4D7D-BB8F-9286B368DF93@exactcode.com>
Date:   Wed, 8 Jul 2020 17:16:41 +0200
From:   René Rebe <rene@...ctcode.com>
To:     linux-kernel@...r.kernel.org
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        viro@...iv.linux.org
Subject: Vectored syscalls Was: [PATCH 0/3] readfile(2): a new syscall to make
 open/read/close faster

Hey there,

maybe instead of this rather specific, niche readfile syscall, would it not be beneficial
to allow issuing any group or bundle of several arbitrary system calls so this could also
be used to speed up other, more demanding high performance applications that need
a bit more than just readfile()?

An iImplementation could use some SYSCALLV syscall taking some io_uring like
structure with a list of flags, syscalls and arguments, so that this case could be submitted
as something like (illustration purposes only):

{
	{ABORT_ON_ERROR, OPEN, …},
	{RET_TO_ARG1, READ, …},
	{0, CLOSE, …},
}

I hope that sounds useful,
	René Rebe

-- 
 ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com
 https://exactscan.com | https://ocrkit.com | https://t2sde.org | https://rene.rebe.de