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
| ||
|
Message-ID: <CA+FuTSeKpOJVqcneCoh_4x4OuK1iE0Tr6f3rSNrQiR-OUgjWow@mail.gmail.com> Date: Thu, 6 Apr 2023 11:34:28 -0400 From: Willem de Bruijn <willemb@...gle.com> To: Breno Leitao <leitao@...ian.org> Cc: io-uring@...r.kernel.org, netdev@...r.kernel.org, kuba@...nel.org, asml.silence@...il.com, axboe@...nel.dk, leit@...com, edumazet@...gle.com, pabeni@...hat.com, davem@...emloft.net, dccp@...r.kernel.org, mptcp@...ts.linux.dev, linux-kernel@...r.kernel.org, dsahern@...nel.org, willemdebruijn.kernel@...il.com, matthieu.baerts@...sares.net, marcelo.leitner@...il.com Subject: Re: [PATCH 0/5] add initial io_uring_cmd support for sockets On Thu, Apr 6, 2023 at 10:45 AM Breno Leitao <leitao@...ian.org> wrote: > > From: Breno Leitao <leit@...com> > > This patchset creates the initial plumbing for a io_uring command for > sockets. > > For now, create two uring commands for sockets, SOCKET_URING_OP_SIOCOUTQ > and SOCKET_URING_OP_SIOCINQ. They are similar to ioctl operations > SIOCOUTQ and SIOCINQ. In fact, the code on the protocol side itself is > heavily based on the ioctl operations. This duplicates all the existing ioctl logic of each protocol. Can this just call the existing proto_ops.ioctl internally and translate from/to io_uring format as needed?
Powered by blists - more mailing lists