From: Linus Torvalds <[email protected]>
To: Jens Axboe <[email protected]>
Cc: io-uring <[email protected]>
Subject: Re: [GIT PULL] io_uring fixes for 6.0-rc1
Date: Fri, 12 Aug 2022 13:28:07 -0700 [thread overview]
Message-ID: <CAHk-=wioqj4HUQM_dXdVoSJtPe+z0KxNrJPg0cs_R3j-gJJxAg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Fri, Aug 12, 2022 at 5:46 AM Jens Axboe <[email protected]> wrote:
>
> - Small series improving type safety of the sqe fields (Stefan)
This doesn't work AT ALL.
A basic allmodconfig build fails with tons of errors. It starts with
In function ‘io_kiocb_cmd_sz_check’,
inlined from ‘io_prep_rw’ at io_uring/rw.c:38:21:
././include/linux/compiler_types.h:354:45: error: call to
‘__compiletime_assert_802’ declared with attribute error: BUILD_BUG_ON
failed: cmd_sz > sizeof(struct io_cmd_data)
354 | _compiletime_assert(condition, msg,
__compiletime_assert_, __COUNTER__)
| ^
././include/linux/compiler_types.h:335:25: note: in definition of
macro ‘__compiletime_assert’
335 | prefix ## suffix();
\
| ^~~~~~
././include/linux/compiler_types.h:354:9: note: in expansion of
macro ‘_compiletime_assert’
354 | _compiletime_assert(condition, msg,
__compiletime_assert_, __COUNTER__)
| ^~~~~~~~~~~~~~~~~~~
./include/linux/build_bug.h:39:37: note: in expansion of macro
‘compiletime_assert’
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^~~~~~~~~~~~~~~~~~
./include/linux/build_bug.h:50:9: note: in expansion of macro
‘BUILD_BUG_ON_MSG’
50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: "
#condition)
| ^~~~~~~~~~~~~~~~
./include/linux/io_uring_types.h:496:9: note: in expansion of macro
‘BUILD_BUG_ON’
496 | BUILD_BUG_ON(cmd_sz > sizeof(struct io_cmd_data));
| ^~~~~~~~~~~~
and goes downhill from there.
I don't think this can have seen any testing at all.
Linus
next prev parent reply other threads:[~2022-08-12 20:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 12:46 [GIT PULL] io_uring fixes for 6.0-rc1 Jens Axboe
2022-08-12 20:28 ` Linus Torvalds [this message]
2022-08-12 20:44 ` Jens Axboe
2022-08-12 21:01 ` Jens Axboe
2022-08-12 21:08 ` Jens Axboe
2022-08-12 21:34 ` Jens Axboe
2022-08-12 21:43 ` Linus Torvalds
2022-08-12 21:53 ` Jens Axboe
2022-08-12 21:54 ` Linus Torvalds
2022-08-12 22:01 ` Linus Torvalds
2022-08-12 22:16 ` Jens Axboe
2022-08-12 22:11 ` Jens Axboe
2022-08-12 22:19 ` Jens Axboe
2022-08-12 22:23 ` Keith Busch
2022-08-12 22:25 ` Jens Axboe
2022-08-12 22:27 ` Jens Axboe
2022-08-12 22:35 ` Linus Torvalds
2022-08-12 22:38 ` Jens Axboe
2022-08-12 22:52 ` Linus Torvalds
2022-08-12 22:55 ` Jens Axboe
2022-08-12 21:37 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2022-08-11 1:01 Jens Axboe
2022-08-11 14:35 ` Jens Axboe
2022-08-13 21:48 ` pr-tracker-bot
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='CAHk-=wioqj4HUQM_dXdVoSJtPe+z0KxNrJPg0cs_R3j-gJJxAg@mail.gmail.com' \
[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