From: Michael Ellerman <mpe@ellerman.id.au>
To: Zhouyi Zhou <zhouzhouyi@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
rcu <rcu@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
lance@osuosl.org, "Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: BUG : PowerPC RCU: torture test failed with __stack_chk_fail
Date: Fri, 28 Apr 2023 00:13:11 +1000 [thread overview]
Message-ID: <87wn1xquq0.fsf@mail.concordia> (raw)
In-Reply-To: <CAABZP2z=xu+07-y5fqFLidZz1VpSgrSwXa1mFHPb=b3Ezr3OtA@mail.gmail.com>
Zhouyi Zhou <zhouzhouyi@gmail.com> writes:
> On Thu, Apr 27, 2023 at 11:09 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> Zhouyi Zhou <zhouzhouyi@gmail.com> writes:
>> > On Tue, Apr 25, 2023 at 2:01 PM Zhouyi Zhou <zhouzhouyi@gmail.com> wrote:
>> >> On Tue, Apr 25, 2023 at 6:07 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>> ...
>> >> >
>> >> > There's 12.2.0 here:
>> >> > https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/12.2.0/
>> >> > https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/ppc64le/12.2.0/
>>
>> > powerpc64le-linux-gnu-gcc-12 cross compiler on my Ubuntu 22.04 does
>> > not seem to have that issue as gcc-10 does
>>
>> OK. So so far it's only that GCC 10 that shows the problem.
>>
>> If you have time, you could use some of the other versions to narrow
>> down which versions show the bug:
>>
>> https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/ppc64le/
>>
>> There's an 11.0, 11.1 and 11.3 there, as well as 9.5 and so on.
> GCC test results (Tested on PPC VM of Open Source Lab of Oregon State
> University)
> gcc 9.4 (ubuntu native): positive, show bug
> gcc 9.5 (download form [1]): positive, show bug
> gcc 10.1 (download from [1]): positive, show bug
> gcc 10.3 (download from [1]): positive, show bug
> gcc 10.4 (download from [1]): positive, show bug
>
> gcc 11.0 (download from [1]): negative, no bug
> gcc 11.1 (download from [1]): negative, no bug
> gcc 11.3 (download from [1]): negative, no bug
> gcc 12.1 (download from [1]): negative, no bug
> gcc 12.2 (download from [1]): negative, no bug
Awesome work.
How are you testing for presence/absence of the bug? By running your
test and seeing if it crashes, or by looking at the generated code?
cheers
next prev parent reply other threads:[~2023-04-27 14:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 12:46 BUG : PowerPC RCU: torture test failed with __stack_chk_fail Zhouyi Zhou
2023-04-22 19:19 ` Joel Fernandes
2023-04-23 1:37 ` Zhouyi Zhou
2023-04-23 5:45 ` Zhouyi Zhou
2023-04-22 19:28 ` Joel Fernandes
2023-04-24 0:32 ` Boqun Feng
2023-04-24 4:00 ` Zhouyi Zhou
2023-04-24 13:14 ` Michael Ellerman
2023-04-24 15:13 ` Segher Boessenkool
2023-04-24 15:28 ` Boqun Feng
2023-04-24 17:29 ` Segher Boessenkool
2023-04-24 19:25 ` Boqun Feng
2023-04-24 18:55 ` Joel Fernandes
2023-04-25 10:13 ` Peter Zijlstra
2023-04-25 10:58 ` Zhouyi Zhou
2023-04-25 11:06 ` Joel Fernandes
2023-04-25 3:12 ` Zhouyi Zhou
2023-04-25 13:40 ` Christophe Leroy
2023-04-25 13:49 ` Zhouyi Zhou
2023-04-26 0:32 ` Joel Fernandes
2023-04-26 1:31 ` Zhouyi Zhou
2023-04-26 2:15 ` Joel Fernandes
2023-04-26 2:37 ` Zhouyi Zhou
2023-04-26 0:42 ` Joel Fernandes
2023-04-26 12:29 ` Michael Ellerman
2023-04-26 13:44 ` Joel Fernandes
2023-04-26 14:20 ` Peter Zijlstra
2023-04-26 14:45 ` Michael Ellerman
2023-04-28 10:35 ` Christophe Leroy
2023-04-25 10:59 ` Joel Fernandes
2023-04-25 11:53 ` Peter Zijlstra
2023-04-25 13:36 ` Christophe Leroy
2023-04-24 22:07 ` Michael Ellerman
2023-04-24 22:13 ` Zhouyi Zhou
2023-04-25 6:01 ` Zhouyi Zhou
2023-04-25 9:27 ` Zhouyi Zhou
2023-04-27 3:09 ` Michael Ellerman
2023-04-27 3:32 ` Zhouyi Zhou
2023-04-27 9:21 ` Zhouyi Zhou
2023-04-27 14:13 ` Michael Ellerman [this message]
2023-04-27 14:29 ` Zhouyi Zhou
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=87wn1xquq0.fsf@mail.concordia \
--to=mpe@ellerman.id.au \
--cc=lance@osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=zhouzhouyi@gmail.com \
/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