From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH 0/3] check errors in early init
Date: Fri, 31 Jan 2025 16:24:20 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
Do the diligence of checking if any of the (inicall) io_uring_init()
fail and if so return an error.
Pavel Begunkov (3):
io_uring: propagate req cache creation errors
io_uring: propagate io_buffer creation errors
io_uring: check for iowq alloc_workqueue errors
io_uring/io_uring.c | 7 +++++++
1 file changed, 7 insertions(+)
--
2.47.1
next reply other threads:[~2025-01-31 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 16:24 Pavel Begunkov [this message]
2025-01-31 16:24 ` [PATCH 1/3] io_uring: propagate req cache creation errors Pavel Begunkov
2025-01-31 16:26 ` Jens Axboe
2025-01-31 16:30 ` Pavel Begunkov
2025-01-31 16:24 ` [PATCH 2/3] io_uring: propagate io_buffer " Pavel Begunkov
2025-01-31 16:24 ` [PATCH 3/3] io_uring: check for iowq alloc_workqueue errors Pavel Begunkov
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