From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
Christian Mazakas <christian.mazakas@gmail.com>,
Michael de Lang <michael@volt-software.nl>,
io-uring Mailing List <io-uring@vger.kernel.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH liburing 1/2] sanitize: Fix missing `IORING_OP_PIPE`
Date: Sat, 26 Jul 2025 00:59:12 +0700 [thread overview]
Message-ID: <20250725175913.2598891-2-ammarfaizi2@gnuweeb.org> (raw)
In-Reply-To: <20250725175913.2598891-1-ammarfaizi2@gnuweeb.org>
Fix build error due to missing `IORING_OP_PIPE`.
```
sanitize.c:122:17: error: static assertion failed due to requirement \
'IORING_OP_WRITEV_FIXED + 1 == IORING_OP_LAST': Need an implementation \
for all IORING_OP_* codes
122 | _Static_assert(IORING_OP_WRITEV_FIXED + 1 == IORING_OP_LAST,\
"Need an implementation for all IORING_OP_* codes");
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
Fixes: eca641e0ea37 ("Add support for IORING_OP_PIPE")
Cc: Michael de Lang <michael@volt-software.nl>
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
src/sanitize.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/sanitize.c b/src/sanitize.c
index 48f794545999..383b7d64bbf2 100644
--- a/src/sanitize.c
+++ b/src/sanitize.c
@@ -119,7 +119,8 @@ static inline void initialize_sanitize_handlers()
sanitize_handlers[IORING_OP_EPOLL_WAIT] = sanitize_sqe_addr;
sanitize_handlers[IORING_OP_READV_FIXED] = sanitize_sqe_addr;
sanitize_handlers[IORING_OP_WRITEV_FIXED] = sanitize_sqe_addr;
- _Static_assert(IORING_OP_WRITEV_FIXED + 1 == IORING_OP_LAST, "Need an implementation for all IORING_OP_* codes");
+ sanitize_handlers[IORING_OP_PIPE] = sanitize_sqe_addr;
+ _Static_assert(IORING_OP_PIPE + 1 == IORING_OP_LAST, "Need an implementation for all IORING_OP_* codes");
sanitize_handlers_initialized = true;
}
--
Ammar Faizi
next prev parent reply other threads:[~2025-07-25 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 17:59 [PATCH liburing 0/2] liburing fixes Ammar Faizi
2025-07-25 17:59 ` Ammar Faizi [this message]
2025-07-25 17:59 ` [PATCH liburing 2/2] liburing: Don't use `IOURINGINLINE` on `__io_uring_prep_poll_mask` Ammar Faizi
2025-07-25 18:21 ` [PATCH liburing 0/2] liburing fixes 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 \
--in-reply-to=20250725175913.2598891-2-ammarfaizi2@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=axboe@kernel.dk \
--cc=christian.mazakas@gmail.com \
--cc=gwml@vger.gnuweeb.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@volt-software.nl \
/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