From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: David Laight <David.Laight@ACULAB.COM>,
"'paulmck@kernel.org'" <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" <rcu@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"trufanov@swemel.ru" <trufanov@swemel.ru>,
"vfh@swemel.ru" <vfh@swemel.ru>
Subject: Re: [PATCH v2] The value may overflow
Date: Tue, 5 Sep 2023 10:34:43 -0400 [thread overview]
Message-ID: <ce51b768-9988-197c-0c35-7574aba77810@efficios.com> (raw)
In-Reply-To: <c312066b2cc44919bd11b6cd938cb05f@AcuMS.aculab.com>
On 9/5/23 10:15, David Laight wrote:
> ...
>> That would instead be more than 512-16=496 CPUs, correct? 496 CPUs would
>> only require a 31-bit shift, which should be OK, but 497 would require
>> a 32-bit shift, which would result in sign extension. If it turns out
>> that sign extension is OK, then we should get in trouble at 513 CPUs,
>> which would result in a 33-bit shift (and is that even defined in C?).
>
> Not quite right :-)
>
> (1 << 31) is int and negative, that gets sign extended before
> being converted to 'unsigned long' - so has the top 33 bits set.
>
> (1 << 32) is undefined, the current x86 cpu ignore the high
> shift bits so it is (1 << 0).
Yes, I was about to reply the same thing. A shift of 31 is buggy,
because shifting 1 << 31 raises the sign bit, which sets the top 33
bits when cast to unsigned long. A shift of 1 << 32 is undefined,
with for instance x86 choosing to ignore the top bit.
But in order to have a 1 << 31 shift from this expression:
sdp->grpmask = 1 << (cpu - sdp->mynode->grplo);
I *think* we need the group to have 32 cpus or more (indexed within
the group from grplo to grplo + 31 (both inclusive)).
So as soon as we have one group with 32 cpus, the problem should show
up. With FANOUT_LEAF=16, we can have 15 groups of 31 cpus and 1
group of 32 cpus, for:
15*31 + 32 = 497 cpus.
AFAIU, this would be the minimum value for smp_processor_id()+1 which
triggers this issue.
Thanks,
Mathieu
>
> If the mask is being used to optimise a search the code might
> just happen to work!
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2023-09-05 17:08 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
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 [this message]
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=ce51b768-9988-197c-0c35-7574aba77810@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=David.Laight@ACULAB.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®