From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Denis Arefev <arefev@swemel.ru>,
Lai Jiangshan <jiangshanlai@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Cc: Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
rcu@vger.kernel.org, lvc-project@linuxtesting.org,
linux-kernel@vger.kernel.org, trufanov@swemel.ru, vfh@swemel.ru
Subject: Re: [PATCH] srcu: The value may overflow
Date: Sat, 2 Sep 2023 10:17:24 -0400 [thread overview]
Message-ID: <c337cc2d-5ae6-5fcd-dce6-658613a4564d@efficios.com> (raw)
In-Reply-To: <d05deed9-637f-697c-5c2f-d6fede4c956d@efficios.com>
On 9/1/23 09:31, Mathieu Desnoyers wrote:
> On 9/1/23 05:53, Denis Arefev wrote:
>> The value of an arithmetic expression 1 << (cpu - sdp->mynode->grplo)
>> is subject to overflow due to a failure to cast operands to a larger
>> data type before performing arithmetic
>>
>> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>>
>> Signed-off-by: Denis Arefev <arefev@swemel.ru>
>> ---
>> kernel/rcu/srcutree.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
>> index 20d7a238d675..e14b74fb1ba0 100644
>> --- a/kernel/rcu/srcutree.c
>> +++ b/kernel/rcu/srcutree.c
>> @@ -223,7 +223,7 @@ static bool init_srcu_struct_nodes(struct
>> srcu_struct *ssp, gfp_t gfp_flags)
>> snp->grplo = cpu;
>> snp->grphi = cpu;
>> }
>> - sdp->grpmask = 1 << (cpu - sdp->mynode->grplo);
>> + sdp->grpmask = 1UL << (cpu - sdp->mynode->grplo);
>
> What possible values of cpus supported by the Linux kernel and grplo can
> cause this to overflow on 64-bit architectures ? I suspect the maximum
> result of this subtraction is defined by the RCU_FANOUT or other srcu
> level-spread values assigned by rcu_init_levelspread(), which can indeed
> cause the signed 32-bit integer literal ("1") to overflow when shifted
> by any value greater than 31. This analysis should be added to the
> commit message so the impact of the issue can be understood.
Another effect that might be worth mentioning in the commit message is
what happens with the sign-carry for "1 << 31" when it is promoted from
signed 32-bit integer to unsigned long on a 64-bit kernel: it translates
to 0xffffffff80000000, which is certainly not what is expected here.
Thanks,
Mathieu
>
> I also notice this in the same file:
>
> srcu_schedule_cbs_snp():
>
> for (cpu = snp->grplo; cpu <= snp->grphi; cpu++) {
> if (!(mask & (1 << (cpu - snp->grplo))))
> continue;
>
> Which should be fixed at the same time.
>
> Thanks,
>
> Mathieu
>
>> }
>> smp_store_release(&ssp->srcu_sup->srcu_size_state,
>> SRCU_SIZE_WAIT_BARRIER);
>> return true;
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2023-09-02 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 9:53 Denis Arefev
2023-09-01 13:31 ` Mathieu Desnoyers
2023-09-02 14:17 ` Mathieu Desnoyers [this message]
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=c337cc2d-5ae6-5fcd-dce6-658613a4564d@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=arefev@swemel.ru \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=trufanov@swemel.ru \
--cc=vfh@swemel.ru \
/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
all inboxes | Powered by JetHome®