From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Denis Arefev <arefev@swemel.ru>, Lai Jiangshan <jiangshanlai@gmail.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
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 v2] The value may overflow
Date: Mon, 4 Sep 2023 06:24:15 -0400 [thread overview]
Message-ID: <bb708695-a513-2006-0985-d6686e525f5a@efficios.com> (raw)
In-Reply-To: <20230904094251.64022-1-arefev@swemel.ru>
On 9/4/23 05:42, 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 patch title should identify more precisely its context, e.g.:
"srcu: Fix srcu_struct node grpmask overflow on 64-bit systems"
Also, as I stated in my reply to the previous version, the patch commit
message should describe the impact of the bug it fixes.
Thanks,
Mathieu
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Signed-off-by: Denis Arefev <arefev@swemel.ru>
> ---
> 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
next prev parent reply other threads:[~2023-09-04 10:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 9:42 Denis Arefev
2023-09-04 10:24 ` Mathieu Desnoyers [this message]
2023-09-05 9:31 ` David Laight
2023-09-05 12:26 ` Mathieu Desnoyers
2023-09-05 13:26 ` Paul E. McKenney
2023-09-05 13:34 ` Mathieu Desnoyers
2023-09-05 13:56 ` Paul E. McKenney
2023-09-05 14:15 ` David Laight
2023-09-05 14:34 ` Mathieu Desnoyers
2023-09-05 16:40 ` Paul E. McKenney
2023-09-05 19:27 ` Paul E. McKenney
2023-09-05 19:36 ` Mathieu Desnoyers
2023-09-05 19:45 ` Paul E. McKenney
2023-09-05 20:40 ` Joel Fernandes
2023-09-05 20:52 ` Paul E. McKenney
2023-09-05 20:56 ` Joel Fernandes
2023-09-05 22:22 ` 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=bb708695-a513-2006-0985-d6686e525f5a@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®