From: Stefan Metzmacher <[email protected]>
To: [email protected], [email protected]
Cc: Stefan Metzmacher <[email protected]>
Subject: [PATCH 0/3] typesafety improvements on io_uring-6.0
Date: Thu, 11 Aug 2022 09:11:13 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Jens,
with the split into individual files (which is gread)
and the introduction of the generic struct io_cmd_data,
we now have the risk do incompatible casting in
io_kiocb_to_cmd().
My patches catch casting problems with BUILD_BUG_ON() now.
While there I added missing BUILD_BUG_ON() checks
for new io_uring_sqe fields.
Stefan Metzmacher (3):
io_uring: consistently make use of io_notif_to_data()
io_uring: make io_kiocb_to_cmd() typesafe
io_uring: add missing BUILD_BUG_ON() checks for new io_uring_sqe
fields
include/linux/io_uring_types.h | 9 +++++++-
io_uring/advise.c | 8 +++----
io_uring/cancel.c | 4 ++--
io_uring/epoll.c | 4 ++--
io_uring/fs.c | 28 +++++++++++------------
io_uring/io_uring.c | 19 ++++++++++++---
io_uring/kbuf.c | 8 +++----
io_uring/msg_ring.c | 8 +++----
io_uring/net.c | 42 +++++++++++++++++-----------------
io_uring/notif.c | 4 +---
io_uring/notif.h | 2 +-
io_uring/openclose.c | 16 ++++++-------
io_uring/poll.c | 16 ++++++-------
io_uring/rsrc.c | 10 ++++----
io_uring/rw.c | 28 +++++++++++------------
io_uring/splice.c | 8 +++----
io_uring/statx.c | 6 ++---
io_uring/sync.c | 12 +++++-----
io_uring/timeout.c | 26 ++++++++++-----------
io_uring/uring_cmd.c | 11 +++++----
io_uring/xattr.c | 18 +++++++--------
21 files changed, 154 insertions(+), 133 deletions(-)
--
2.34.1
next reply other threads:[~2022-08-11 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 7:11 Stefan Metzmacher [this message]
2022-08-11 7:11 ` [PATCH 1/3] io_uring: consistently make use of io_notif_to_data() Stefan Metzmacher
2022-08-11 7:11 ` [PATCH 2/3] io_uring: make io_kiocb_to_cmd() typesafe Stefan Metzmacher
2022-08-11 7:11 ` [PATCH 3/3] io_uring: add missing BUILD_BUG_ON() checks for new io_uring_sqe fields Stefan Metzmacher
2022-08-11 15:38 ` [PATCH 0/3] typesafety improvements on io_uring-6.0 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] \
[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