From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET 0/2] Sanitize request setup
Date: Sat, 16 Mar 2024 11:29:33 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
Just two minor patches, one ensuring the networking side preps anything
in req->cmd upfront (more of a cleanup to be nice), and one fixing
calling into ->fail() if prep hasn't been run yet. The nice thing about
patch 2 is that it moves the error stuff mostly ouside of the
io_init_req() hot path, and as a result reduces the text size by 232 bytes.
--
Jens Axboe
next reply other threads:[~2024-03-16 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 17:29 Jens Axboe [this message]
2024-03-16 17:29 ` [PATCH 1/2] io_uring/net: ensure async prep handlers always initialize ->done_io Jens Axboe
2024-03-16 17:29 ` [PATCH 2/2] io_uring: clear opcode specific data for an early failure 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