From: Pavel Begunkov <[email protected]>
To: Hao Xu <[email protected]>, Jens Axboe <[email protected]>
Cc: [email protected], Joseph Qi <[email protected]>
Subject: Re: [PATCH] io_uring: fix bug of wrong BUILD_BUG_ON check
Date: Mon, 6 Sep 2021 20:15:50 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/6/21 6:03 PM, Hao Xu wrote:
> 在 2021/9/6 下午11:22, Pavel Begunkov 写道:
>> On 9/6/21 4:12 PM, Hao Xu wrote:
>>> Some check should be large than not equal or large than.
>>>
>>> Signed-off-by: Hao Xu <[email protected]>
>>> ---
>>> fs/io_uring.c | 6 +++---
>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/fs/io_uring.c b/fs/io_uring.c
>>> index 2bde732a1183..3a833037af43 100644
>>> --- a/fs/io_uring.c
>>> +++ b/fs/io_uring.c
>>> @@ -10637,13 +10637,13 @@ static int __init io_uring_init(void)
>>> sizeof(struct io_uring_rsrc_update2));
>>> /* ->buf_index is u16 */
>>> - BUILD_BUG_ON(IORING_MAX_REG_BUFFERS >= (1u << 16));
>>> + BUILD_BUG_ON(IORING_MAX_REG_BUFFERS > (1u << 16));
>>> /* should fit into one byte */
>>> - BUILD_BUG_ON(SQE_VALID_FLAGS >= (1 << 8));
>>> + BUILD_BUG_ON(SQE_VALID_FLAGS > (1 << 8));
>>
>> 0xff = 255 is the largest number fitting in u8,
>> 1<<8 = 256.
>>
>> let SQE_VALID_FLAGS = 256,
>> (256 > (1<<8)) == (256 > 256) == false, even though it can't
>> be represented by u8.
> Isn't SQE_VALID_FLAGS = 256 a valid value for it?
SQE_VALID_FLAGS is a "bitwise OR" combination of valid flags, so
can't be go beyond 0xff
>>
>>
>>> BUILD_BUG_ON(ARRAY_SIZE(io_op_defs) != IORING_OP_LAST);
>>> - BUILD_BUG_ON(__REQ_F_LAST_BIT >= 8 * sizeof(int));
>>> + BUILD_BUG_ON(__REQ_F_LAST_BIT > 8 * sizeof(int));
>>> req_cachep = KMEM_CACHE(io_kiocb, SLAB_HWCACHE_ALIGN | SLAB_PANIC |
>>> SLAB_ACCOUNT);
>>>
>>
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-09-06 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 15:12 [PATCH] io_uring: fix bug of wrong BUILD_BUG_ON check Hao Xu
2021-09-06 15:22 ` Pavel Begunkov
2021-09-06 17:03 ` Hao Xu
2021-09-06 19:15 ` Pavel Begunkov [this message]
2021-09-07 3:02 ` Hao Xu
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] \
[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