Stack protector crash in pnv_smp_cpu_kill_self()

[Christophe LEROY]

Looks like a lack of initialisation of the canary for the non-boot CPUs 
on SMP, you applied this morning the patch I sent you for that.

Is the patch in ?

Christophe

Le 15/10/2018 à 15:26, Michael Ellerman a écrit :
> Hi all,
> 
> Spotted this today, haven't had time to debug it further, just FYI in
> case anyone else sees it.
> 
>    Running tests in cpufreq
>    ========================================
>    selftests: cpufreq: main.sh
>    pid 9727's current affinity mask: ffffffffffffffffffffffffffffffffffffffffffff
>    pid 9727's new affinity mask: 1
>    Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: pnv_smp_cpu_kill_self+0x2a0/0x2b0
>    
>    CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.19.0-rc3-gcc-7.3.1-00168-g4ffe713b7587 #94
>    Call Trace:
>    [c000000007a1fb00] [c000000000ae7b4c] dump_stack+0xb0/0xf4 (unreliable)
>    [c000000007a1fb40] [c0000000000e59cc] panic+0x144/0x328
>    [c000000007a1fbe0] [c0000000000e544c] __stack_chk_fail+0x2c/0x30
>    [c000000007a1fc40] [c00000000009eca0] pnv_smp_cpu_kill_self+0x2a0/0x2b0
>    [c000000007a1fe10] [c0000000000475f8] cpu_die+0x48/0x70
>    [c000000007a1fe30] [c000000000020620] arch_cpu_idle_dead+0x20/0x40
>    [c000000007a1fe50] [c00000000012da94] do_idle+0x274/0x390
>    [c000000007a1fec0] [c00000000012de08] cpu_startup_entry+0x38/0x50
>    [c000000007a1fef0] [c000000000047334] start_secondary+0x5e4/0x600
>    [c000000007a1ff90] [c00000000000ac70] start_secondary_prolog+0x10/0x14
>    Rebooting in 10 seconds..
>    [39378.502863506,5] OPAL: Reboot request
> 
> 
> 
> cheers
>