mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: paulmck@kernel.org
Cc: Denis Arefev <arefev@swemel.ru>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	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,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v3] Fix srcu_struct node grpmask overflow on 64-bit systems
Date: Tue, 5 Sep 2023 08:57:53 -0400	[thread overview]
Message-ID: <7beb35c3-217a-d3c3-8e75-a1212500d2ac@efficios.com> (raw)
In-Reply-To: <751d2afd-fc91-400d-8889-187031f2bbf0@paulmck-laptop>

On 9/4/23 09:58, Paul E. McKenney wrote:
> On Mon, Sep 04, 2023 at 08:58:48AM -0400, Mathieu Desnoyers wrote:
>> On 9/4/23 08:42, Mathieu Desnoyers wrote:
>>> On 9/4/23 08:21, 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.
>>>>
>>>> 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.
>>>
>>> We could expand on this:
>>>
>>> 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 on a 64-bit system.
>>>
>>> Moreover, when the subtraction value is 31, the 1 << 31 expression results
>>> in 0xffffffff80000000 when the signed integer is promoted to unsigned long
>>> on 64-bit systems due to type promotion rules, which is certainly not the
>>> intended result.
> 
> Thank you both!  Could you please also add something to the effect of:
> "Given default Kconfig options, this bug affects only systems with more
> than 512 CPUs."?

Hi Paul,

I'm trying to understand this "NR_CPUS > 512 CPUs" default Kconfig lower 
bound from kernel/rcu/Kconfig and rcu_node_tree.h. Is that on a 32-bit 
or 64-bit architecture ? Also, I suspect that something like x86-64 
MAXSMP (or an explicit NR_CPUS) needs to be selected over a default 
Kconfig to support that many CPUs.

Thanks,

Mathieu


> 
> 							Thanx, Paul
> 
>>>> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>>>
>>> With the commit message updated with my comment above, please also add:
>>>
>>> Fixes: c7e88067c1 ("srcu: Exact tracking of srcu_data structures
>>> containing callbacks")
>>> Cc: <stable@vger.kernel.org> # v4.11
>>
>> Sorry, the line above should read:
>>
>> Cc: <stable@vger.kernel.org> # v4.11+
>>
>> Thanks,
>>
>> Mathieu
>>
>>> Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>>>
>>> Thanks!
>>>
>>> Mathieu
>>>
>>>>
>>>> Signed-off-by: Denis Arefev <arefev@swemel.ru>
>>>> ---
>>>> v3: Changed the name of the patch, as suggested by
>>>> Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>>>> v2: Added fixes to the srcu_schedule_cbs_snp function as suggested by
>>>> Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>>>>    kernel/rcu/srcutree.c | 4 ++--
>>>>    1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
>>>> index 20d7a238d675..6c18e6005ae1 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);
>>>>        }
>>>>        smp_store_release(&ssp->srcu_sup->srcu_size_state,
>>>> SRCU_SIZE_WAIT_BARRIER);
>>>>        return true;
>>>> @@ -833,7 +833,7 @@ static void srcu_schedule_cbs_snp(struct
>>>> srcu_struct *ssp, struct srcu_node *snp
>>>>        int cpu;
>>>>        for (cpu = snp->grplo; cpu <= snp->grphi; cpu++) {
>>>> -        if (!(mask & (1 << (cpu - snp->grplo))))
>>>> +        if (!(mask & (1UL << (cpu - snp->grplo))))
>>>>                continue;
>>>>            srcu_schedule_cbs_sdp(per_cpu_ptr(ssp->sda, cpu), delay);
>>>>        }
>>>
>>
>> -- 
>> Mathieu Desnoyers
>> EfficiOS Inc.
>> https://www.efficios.com
>>

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com


  reply	other threads:[~2023-09-05 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 12:21 Denis Arefev
2023-09-04 12:42 ` Mathieu Desnoyers
2023-09-04 12:58   ` Mathieu Desnoyers
2023-09-04 13:58     ` Paul E. McKenney
2023-09-05 12:57       ` Mathieu Desnoyers [this message]
2023-09-05 13:38         ` Paul E. McKenney
2023-09-05 13:43           ` Mathieu Desnoyers
2023-09-05 14:00             ` Paul E. McKenney

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=7beb35c3-217a-d3c3-8e75-a1212500d2ac@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=stable@vger.kernel.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®