netdev - Re: [RFC PATCH v2 1/4] net: wire up support for file_operations->uring

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: <d289ab2c-dd5a-fd35-2a2a-7ccdfb947873@kernel.org>
Date: Mon, 19 Jun 2023 19:09:27 -0700
From: David Ahern <dsahern@...nel.org>
To: Pavel Begunkov <asml.silence@...il.com>, Breno Leitao
 <leitao@...ian.org>, io-uring@...r.kernel.org, axboe@...nel.dk,
 davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, Matthieu Baerts <matthieu.baerts@...sares.net>,
 Mat Martineau <martineau@...nel.org>,
 Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
 Xin Long <lucien.xin@...il.com>
Cc: leit@...com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
 dccp@...r.kernel.org, mptcp@...ts.linux.dev, linux-sctp@...r.kernel.org,
 ast@...nel.org, kuniyu@...zon.com, martin.lau@...nel.org,
 Jason Xing <kernelxing@...cent.com>, Joanne Koong <joannelkoong@...il.com>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 "Jason A. Donenfeld" <Jason@...c4.com>, Willem de Bruijn
 <willemb@...gle.com>, Guillaume Nault <gnault@...hat.com>,
 Andrea Righi <andrea.righi@...onical.com>
Subject: Re: [RFC PATCH v2 1/4] net: wire up support for
 file_operations->uring_cmd()

On 6/19/23 2:28 AM, Pavel Begunkov wrote:
> That callback is all about file dependent operations, just like ioctl.
> And as the patch in question is doing socket specific stuff, I think
> architecturally it fits well. I also believe Breno wants to extend it
> later to support more operations.
> 
> Sockets are a large chunk of use cases, it can be implemented as a
> separate io_uring request type if nothing else works, but in general
> that might not be as scalable.

The io_uring commands are wrappers to existing networking APIs - doing
via io_uring what userspace apps can do via system calls. As such, the
translations should be done in io_uring code and then invoking in-kernel
APIs.

Same comment applies to sockopts when those come around and any other
future extensions.