public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH 0/7] improve net msghdr / iovec handlng
Date: Wed, 26 Feb 2025 11:41:14 +0000	[thread overview]
Message-ID: <[email protected]> (raw)

Note: depends on ("io_uring/net: save msg_control for compat")

Continuing refactoring how iovecs are treated, this series adds
some more sanity to handling struct msghdr in the networking code.
We can do some more cleaning on top, but it should be in a good
shape, and it'll be easier to do new stuff with that in.

Pavel Begunkov (7):
  io_uring/net: remove unnecessary REQ_F_NEED_CLEANUP
  io_uring/net: simplify compat selbuf iov parsing
  io_uring/net: isolate msghdr copying code
  io_uring/net: verify msghdr before copying iovec
  io_uring/net: derive iovec storage later
  io_uring/net: unify *mshot_prep calls with compat
  io_uring/net: extract iovec import into a helper

 io_uring/net.c | 180 ++++++++++++++++++++++---------------------------
 1 file changed, 81 insertions(+), 99 deletions(-)

-- 
2.48.1


             reply	other threads:[~2025-02-26 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 11:41 Pavel Begunkov [this message]
2025-02-26 11:41 ` [PATCH 1/7] io_uring/net: remove unnecessary REQ_F_NEED_CLEANUP Pavel Begunkov
2025-02-26 11:41 ` [PATCH 2/7] io_uring/net: simplify compat selbuf iov parsing Pavel Begunkov
2025-02-26 11:41 ` [PATCH 3/7] io_uring/net: isolate msghdr copying code Pavel Begunkov
2025-02-26 11:41 ` [PATCH 4/7] io_uring/net: verify msghdr before copying iovec Pavel Begunkov
2025-02-26 11:41 ` [PATCH 5/7] io_uring/net: derive iovec storage later Pavel Begunkov
2025-02-26 11:41 ` [PATCH 6/7] io_uring/net: unify *mshot_prep calls with compat Pavel Begunkov
2025-02-26 11:41 ` [PATCH 7/7] io_uring/net: extract iovec import into a helper Pavel Begunkov
2025-02-26 17:41 ` [PATCH 0/7] improve net msghdr / iovec handlng Jens Axboe

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox