From: Breno Leitao <leitao@debian.org>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 0/5] add initial io_uring_cmd support for sockets
Date: Wed, 12 Apr 2023 13:53:30 +0000 [thread overview]
Message-ID: <ZDa32u9RNI4NQ7Ko@gmail.com> (raw)
In-Reply-To: <20230406144330.1932798-1-leitao@debian.org>
On Tue, Apr 11, 2023 at 09:28:29AM -0600, Jens Axboe wrote:
> On 4/11/23 9:24?AM, Willem de Bruijn wrote:
> > Jens Axboe wrote:
> >> On 4/11/23 9:00?AM, Willem de Bruijn wrote:
> >> But that doesn't work, because sock->ops->ioctl() assumes the arg is
> >> memory in userspace. Or do you mean change all of the sock->ops->ioctl()
> >> to pass in on-stack memory (or similar) and have it work with a kernel
> >> address?
> >
> > That was what I suggested indeed.
> >
> > It's about as much code change as this patch series. But it avoids
> > the code duplication.
>
> Breno, want to tackle that as a prep patch first? Should make the
> functional changes afterwards much more straightforward, and will allow
> support for anything really.
Absolutely. I just want to make sure that I got the proper approach that
we agreed here.
Let me explain what I understood taking TCP as an example:
1) Rename tcp_ioctl() to something as _tcp_ioctl() where the 'arg'
argument is now just a kernel memory (located in the stack frame from the
callee).
2) Recreate "tcp_ioctl()" that will basically allocate a 'arg' in the
stack and call _tcp_ioctl() passing that 'arg' argument. At the bottom of
this (tcp_ioctl() function) function, call `put_user(in_kernel_arg, userspace_arg)
3) Repeat it for the 20 protocols that implement ioctl:
ag "struct proto .* = {" -A 20 net/ | grep \.ioctl
net/dccp/ipv6.c .ioctl = dccp_ioctl,
net/dccp/ipv4.c .ioctl = dccp_ioctl,
net/ieee802154/socket.c .ioctl = dgram_ioctl,
net/ipv4/udplite.c .ioctl = udp_ioctl,
net/ipv4/raw.c .ioctl = raw_ioctl,
net/ipv4/udp.c .ioctl = udp_ioctl,
net/ipv4/tcp_ipv4.c .ioctl = tcp_ioctl,
net/ipv6/raw.c .ioctl = rawv6_ioctl,
net/ipv6/tcp_ipv6.c .ioctl = tcp_ioctl,
net/ipv6/udp.c .ioctl = udp_ioctl,
net/ipv6/udplite.c .ioctl = udp_ioctl,
net/l2tp/l2tp_ip6.c .ioctl = l2tp_ioctl,
net/l2tp/l2tp_ip.c .ioctl = l2tp_ioctl,
net/phonet/datagram.: .ioctl = pn_ioctl,
net/phonet/pep.c .ioctl = pep_ioctl,
net/rds/af_rds.c .ioctl = rds_ioctl,
net/sctp/socket.c .ioctl = sctp_ioctl,
net/sctp/socket.c .ioctl = sctp_ioctl,
net/xdp/xsk.c .ioctl = sock_no_ioctl,
net/mptcp/protocol.c .ioctl = mptcp_ioctl,
Am I missing something?
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Breno Leitao <leitao@debian.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
David Ahern <dsahern@kernel.org>,
Willem de Bruijn <willemb@google.com>,
io-uring@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org, asml.silence@gmail.com, leit@fb.com,
edumazet@google.com, pabeni@redhat.com, davem@davemloft.net,
dccp@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org, matthieu.baerts@tessares.net,
marcelo.leitner@gmail.com
Subject: Re: [PATCH 0/5] add initial io_uring_cmd support for sockets
Date: Wed, 12 Apr 2023 06:53:30 -0700 [thread overview]
Message-ID: <ZDa32u9RNI4NQ7Ko@gmail.com> (raw)
In-Reply-To: <20cb4641-c765-e5ef-41cb-252be7721ce5@kernel.dk>
On Tue, Apr 11, 2023 at 09:28:29AM -0600, Jens Axboe wrote:
> On 4/11/23 9:24?AM, Willem de Bruijn wrote:
> > Jens Axboe wrote:
> >> On 4/11/23 9:00?AM, Willem de Bruijn wrote:
> >> But that doesn't work, because sock->ops->ioctl() assumes the arg is
> >> memory in userspace. Or do you mean change all of the sock->ops->ioctl()
> >> to pass in on-stack memory (or similar) and have it work with a kernel
> >> address?
> >
> > That was what I suggested indeed.
> >
> > It's about as much code change as this patch series. But it avoids
> > the code duplication.
>
> Breno, want to tackle that as a prep patch first? Should make the
> functional changes afterwards much more straightforward, and will allow
> support for anything really.
Absolutely. I just want to make sure that I got the proper approach that
we agreed here.
Let me explain what I understood taking TCP as an example:
1) Rename tcp_ioctl() to something as _tcp_ioctl() where the 'arg'
argument is now just a kernel memory (located in the stack frame from the
callee).
2) Recreate "tcp_ioctl()" that will basically allocate a 'arg' in the
stack and call _tcp_ioctl() passing that 'arg' argument. At the bottom of
this (tcp_ioctl() function) function, call `put_user(in_kernel_arg, userspace_arg)
3) Repeat it for the 20 protocols that implement ioctl:
ag "struct proto .* = {" -A 20 net/ | grep \.ioctl
net/dccp/ipv6.c .ioctl = dccp_ioctl,
net/dccp/ipv4.c .ioctl = dccp_ioctl,
net/ieee802154/socket.c .ioctl = dgram_ioctl,
net/ipv4/udplite.c .ioctl = udp_ioctl,
net/ipv4/raw.c .ioctl = raw_ioctl,
net/ipv4/udp.c .ioctl = udp_ioctl,
net/ipv4/tcp_ipv4.c .ioctl = tcp_ioctl,
net/ipv6/raw.c .ioctl = rawv6_ioctl,
net/ipv6/tcp_ipv6.c .ioctl = tcp_ioctl,
net/ipv6/udp.c .ioctl = udp_ioctl,
net/ipv6/udplite.c .ioctl = udp_ioctl,
net/l2tp/l2tp_ip6.c .ioctl = l2tp_ioctl,
net/l2tp/l2tp_ip.c .ioctl = l2tp_ioctl,
net/phonet/datagram.: .ioctl = pn_ioctl,
net/phonet/pep.c .ioctl = pep_ioctl,
net/rds/af_rds.c .ioctl = rds_ioctl,
net/sctp/socket.c .ioctl = sctp_ioctl,
net/sctp/socket.c .ioctl = sctp_ioctl,
net/xdp/xsk.c .ioctl = sock_no_ioctl,
net/mptcp/protocol.c .ioctl = mptcp_ioctl,
Am I missing something?
Thanks!
next prev parent reply other threads:[~2023-04-12 13:53 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 14:43 [PATCH 0/5] add initial io_uring_cmd support for sockets Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 15:34 ` Willem de Bruijn
2023-04-06 15:34 ` Willem de Bruijn
2023-04-06 15:59 ` Breno Leitao
2023-04-06 15:59 ` Breno Leitao
2023-04-06 16:41 ` Keith Busch
2023-04-06 16:41 ` Keith Busch
2023-04-06 16:49 ` Jens Axboe
2023-04-06 16:49 ` Jens Axboe
2023-04-06 16:58 ` Breno Leitao
2023-04-06 16:58 ` Breno Leitao
2023-04-06 18:16 ` Willem de Bruijn
2023-04-06 18:16 ` Willem de Bruijn
2023-04-07 2:46 ` David Ahern
2023-04-07 2:46 ` David Ahern
2023-04-11 11:59 ` Breno Leitao
2023-04-11 12:00 ` Breno Leitao
2023-04-11 14:36 ` David Ahern
2023-04-11 14:36 ` David Ahern
2023-04-11 14:41 ` Jens Axboe
2023-04-11 14:41 ` Jens Axboe
2023-04-11 14:51 ` Willem de Bruijn
2023-04-11 14:51 ` Willem de Bruijn
2023-04-11 14:54 ` Jens Axboe
2023-04-11 14:54 ` Jens Axboe
2023-04-11 15:00 ` Willem de Bruijn
2023-04-11 15:00 ` Willem de Bruijn
2023-04-11 15:06 ` Jens Axboe
2023-04-11 15:06 ` Jens Axboe
2023-04-11 15:10 ` David Ahern
2023-04-11 15:10 ` David Ahern
2023-04-11 15:17 ` Jens Axboe
2023-04-11 15:17 ` Jens Axboe
2023-04-11 15:24 ` Willem de Bruijn
2023-04-11 15:24 ` Willem de Bruijn
2023-04-11 15:27 ` David Ahern
2023-04-11 15:27 ` David Ahern
2023-04-11 15:28 ` Jens Axboe
2023-04-11 15:28 ` Jens Axboe
2023-04-11 15:29 ` Jens Axboe
2023-04-11 15:29 ` Jens Axboe
2023-04-12 7:39 ` David Laight
2023-04-12 7:39 ` David Laight
2023-04-12 13:53 ` Breno Leitao [this message]
2023-04-12 13:53 ` Breno Leitao
2023-04-12 14:28 ` Willem de Bruijn
2023-04-12 14:28 ` Willem de Bruijn
2023-04-13 0:02 ` Breno Leitao
2023-04-13 0:02 ` Breno Leitao
2023-04-13 14:24 ` Willem de Bruijn
2023-04-13 14:24 ` Willem de Bruijn
2023-04-13 14:45 ` Jakub Kicinski
2023-04-13 14:45 ` Jakub Kicinski
2023-04-13 14:57 ` David Laight
2023-04-13 14:57 ` David Laight
2023-04-18 13:23 ` Breno Leitao
2023-04-18 13:23 ` Breno Leitao
2023-04-18 19:41 ` Willem de Bruijn
2023-04-18 19:41 ` Willem de Bruijn
2023-04-20 14:43 ` Breno Leitao
2023-04-20 14:43 ` Breno Leitao
2023-04-20 16:48 ` Willem de Bruijn
2023-04-20 16:48 ` Willem de Bruijn
2023-05-02 9:21 ` Adrien Delorme
2023-05-02 9:21 ` Adrien Delorme
2023-05-02 13:03 ` Pavel Begunkov
2023-05-02 13:03 ` Pavel Begunkov
2023-05-03 13:11 ` Adrien Delorme
2023-05-03 13:11 ` Adrien Delorme
2023-05-03 13:27 ` David Laight
2023-05-03 13:27 ` David Laight
-- strict thread matches above, loose matches on Subject: below --
2023-04-06 14:43 [RFC PATCH 1/4] net: wire up support for file_operations->uring_cmd() Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 14:43 [RFC PATCH 2/4] net: add uring_cmd callback to UDP Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 19:03 ` kernel test robot
2023-04-11 12:54 ` Pavel Begunkov
2023-04-11 12:54 ` Pavel Begunkov
2023-04-06 14:43 [RFC PATCH 3/4] net: add uring_cmd callback to TCP Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 20:35 ` kernel test robot
2023-04-06 14:43 [RFC PATCH 4/4] net: add uring_cmd callback to raw "protocol" Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 16:57 [PATCH RFC] io_uring: Pass whole sqe to commands Breno Leitao
2023-04-06 16:57 ` Breno Leitao
2023-04-06 17:50 ` io_uring: Pass whole sqe to commands: Tests Results MPTCP CI
2023-04-07 18:51 ` [PATCH RFC] io_uring: Pass whole sqe to commands Keith Busch
2023-04-07 18:51 ` Keith Busch
2023-04-07 19:43 ` io_uring: Pass whole sqe to commands: Tests Results MPTCP CI
2023-04-11 12:22 ` [PATCH RFC] io_uring: Pass whole sqe to commands Breno Leitao
2023-04-11 12:22 ` Breno Leitao
2023-04-11 12:39 ` Pavel Begunkov
2023-04-11 12:39 ` Pavel Begunkov
2023-04-13 2:56 ` Ming Lei
2023-04-13 2:56 ` Ming Lei
2023-04-13 16:47 ` Breno Leitao
2023-04-13 16:47 ` Breno Leitao
2023-04-14 2:12 ` Ming Lei
2023-04-14 2:12 ` Ming Lei
2023-04-14 13:12 ` Pavel Begunkov
2023-04-14 13:12 ` Pavel Begunkov
2023-04-14 13:59 ` Ming Lei
2023-04-14 13:59 ` Ming Lei
2023-04-14 14:56 ` Pavel Begunkov
2023-04-14 14:56 ` Pavel Begunkov
2023-04-16 9:51 ` Ming Lei
2023-04-16 9:51 ` Ming Lei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZDa32u9RNI4NQ7Ko@gmail.com \
--to=leitao@debian.org \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.