From: Michael Ellerman <mpe@ellerman.id.au>
To: Peter Zijlstra <peterz@infradead.org>,
Joel Fernandes <joel@joelfernandes.org>
Cc: Christophe Leroy <christophe.leroy@c-s.fr>,
"Paul E. McKenney" <paulmck@kernel.org>,
Zhouyi Zhou <zhouzhouyi@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
rcu <rcu@vger.kernel.org>,
lance@osuosl.org, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: BUG : PowerPC RCU: torture test failed with __stack_chk_fail
Date: Thu, 27 Apr 2023 00:45:44 +1000 [thread overview]
Message-ID: <874jp2zopz.fsf@mail.concordia> (raw)
In-Reply-To: <20230426142054.GA1381951@hirez.programming.kicks-ass.net>
Peter Zijlstra <peterz@infradead.org> writes:
> On Wed, Apr 26, 2023 at 09:44:22AM -0400, Joel Fernandes wrote:
>
>> How could you control which code paths don't have the stack protector?
>> Just curious.
>
> https://lkml.kernel.org/r/20230412-no_stackp-v2-0-116f9fe4bbe7@google.com
We also have some entire files disabled, eg:
$ git grep no-stack-protector arch/powerpc/
arch/powerpc/kernel/Makefile:CFLAGS_prom_init.o += -fno-stack-protector
arch/powerpc/kernel/Makefile:CFLAGS_syscall.o += -fno-stack-protector
arch/powerpc/kernel/Makefile:CFLAGS_setup_64.o += -fno-stack-protector
arch/powerpc/kernel/Makefile:CFLAGS_paca.o += -fno-stack-protector
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Peter Zijlstra <peterz@infradead.org>,
Joel Fernandes <joel@joelfernandes.org>
Cc: Zhouyi Zhou <zhouzhouyi@gmail.com>,
Christophe Leroy <christophe.leroy@c-s.fr>,
Boqun Feng <boqun.feng@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
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: Thu, 27 Apr 2023 00:45:44 +1000 [thread overview]
Message-ID: <874jp2zopz.fsf@mail.concordia> (raw)
In-Reply-To: <20230426142054.GA1381951@hirez.programming.kicks-ass.net>
Peter Zijlstra <peterz@infradead.org> writes:
> On Wed, Apr 26, 2023 at 09:44:22AM -0400, Joel Fernandes wrote:
>
>> How could you control which code paths don't have the stack protector?
>> Just curious.
>
> https://lkml.kernel.org/r/20230412-no_stackp-v2-0-116f9fe4bbe7@google.com
We also have some entire files disabled, eg:
$ git grep no-stack-protector arch/powerpc/
arch/powerpc/kernel/Makefile:CFLAGS_prom_init.o += -fno-stack-protector
arch/powerpc/kernel/Makefile:CFLAGS_syscall.o += -fno-stack-protector
arch/powerpc/kernel/Makefile:CFLAGS_setup_64.o += -fno-stack-protector
arch/powerpc/kernel/Makefile:CFLAGS_paca.o += -fno-stack-protector
cheers
next prev parent reply other threads:[~2023-04-26 14:46 UTC|newest]
Thread overview: 80+ 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-22 19:19 ` Joel Fernandes
2023-04-23 1:37 ` Zhouyi Zhou
2023-04-23 1:37 ` Zhouyi Zhou
2023-04-23 5:45 ` Zhouyi Zhou
2023-04-23 5:45 ` Zhouyi Zhou
2023-04-22 19:28 ` Joel Fernandes
2023-04-22 19:28 ` Joel Fernandes
2023-04-24 0:32 ` Boqun Feng
2023-04-24 0:32 ` Boqun Feng
2023-04-24 4:00 ` Zhouyi Zhou
2023-04-24 4:00 ` Zhouyi Zhou
2023-04-24 13:14 ` Michael Ellerman
2023-04-24 13:14 ` Michael Ellerman
2023-04-24 15:13 ` Segher Boessenkool
2023-04-24 15:13 ` Segher Boessenkool
2023-04-24 15:28 ` Boqun Feng
2023-04-24 15:28 ` Boqun Feng
2023-04-24 17:29 ` Segher Boessenkool
2023-04-24 17:29 ` Segher Boessenkool
2023-04-24 19:25 ` Boqun Feng
2023-04-24 19:25 ` Boqun Feng
2023-04-24 18:55 ` Joel Fernandes
2023-04-24 18:55 ` Joel Fernandes
2023-04-25 10:13 ` Peter Zijlstra
2023-04-25 10:13 ` Peter Zijlstra
2023-04-25 10:58 ` Zhouyi Zhou
2023-04-25 10:58 ` Zhouyi Zhou
2023-04-25 11:06 ` Joel Fernandes
2023-04-25 11:06 ` Joel Fernandes
2023-04-25 3:12 ` Zhouyi Zhou
2023-04-25 3:12 ` Zhouyi Zhou
2023-04-25 13:40 ` Christophe Leroy
2023-04-25 13:40 ` Christophe Leroy
2023-04-25 13:49 ` Zhouyi Zhou
2023-04-25 13:49 ` Zhouyi Zhou
2023-04-26 0:32 ` Joel Fernandes
2023-04-26 0:32 ` Joel Fernandes
2023-04-26 1:31 ` Zhouyi Zhou
2023-04-26 1:31 ` Zhouyi Zhou
2023-04-26 2:15 ` Joel Fernandes
2023-04-26 2:15 ` Joel Fernandes
2023-04-26 2:37 ` Zhouyi Zhou
2023-04-26 2:37 ` Zhouyi Zhou
2023-04-26 0:42 ` Joel Fernandes
2023-04-26 0:42 ` Joel Fernandes
2023-04-26 12:29 ` Michael Ellerman
2023-04-26 12:29 ` Michael Ellerman
2023-04-26 13:44 ` Joel Fernandes
2023-04-26 13:44 ` Joel Fernandes
2023-04-26 14:20 ` Peter Zijlstra
2023-04-26 14:20 ` Peter Zijlstra
2023-04-26 14:45 ` Michael Ellerman [this message]
2023-04-26 14:45 ` Michael Ellerman
2023-04-28 10:35 ` Christophe Leroy
2023-04-28 10:35 ` Christophe Leroy
2023-04-25 10:59 ` Joel Fernandes
2023-04-25 10:59 ` Joel Fernandes
2023-04-25 11:53 ` Peter Zijlstra
2023-04-25 11:53 ` Peter Zijlstra
2023-04-25 13:36 ` Christophe Leroy
2023-04-25 13:36 ` Christophe Leroy
2023-04-24 22:07 ` Michael Ellerman
2023-04-24 22:13 ` Zhouyi Zhou
2023-04-24 22:13 ` Zhouyi Zhou
2023-04-25 6:01 ` Zhouyi Zhou
2023-04-25 6:01 ` Zhouyi Zhou
2023-04-25 9:27 ` Zhouyi Zhou
2023-04-25 9:27 ` Zhouyi Zhou
2023-04-27 3:09 ` Michael Ellerman
2023-04-27 3:09 ` Michael Ellerman
2023-04-27 3:32 ` Zhouyi Zhou
2023-04-27 3:32 ` Zhouyi Zhou
2023-04-27 9:21 ` Zhouyi Zhou
2023-04-27 9:21 ` Zhouyi Zhou
2023-04-27 14:13 ` Michael Ellerman
2023-04-27 14:13 ` Michael Ellerman
2023-04-27 14:29 ` Zhouyi Zhou
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=874jp2zopz.fsf@mail.concordia \
--to=mpe@ellerman.id.au \
--cc=boqun.feng@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=joel@joelfernandes.org \
--cc=lance@osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.