Thread (23 messages) 23 messages, 3 authors, 2019-01-25

Re: [PATCH v13 00/10] powerpc: Switch to CONFIG_THREAD_INFO_IN_TASK

From: Michael Ellerman <mpe@ellerman.id.au>
Date: 2019-01-23 23:10:43
Also in: lkml

LEROY Christophe [off-list ref] writes:
Michael Ellerman [off-list ref] a écrit :
quoted
Christophe Leroy [off-list ref] writes:
quoted
The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK which
moves the thread_info into task_struct.

Moving thread_info into task_struct has the following advantages:
- It protects thread_info from corruption in the case of stack
overflows.
- Its address is harder to determine if stack addresses are
leaked, making a number of attacks more difficult.

Changes since v12:
 - Patch 1: Taken comment from Mike (re-introduced the 'panic' in  
case memblock allocation fails in setup_64.c
 - Patch 1: Added alloc_stack() function in setup_32.c to also  
panic in case of allocation failure.
Hi Christophe,

I can't get this series to boot on qemu mac99. I'm getting eg:
Problem new with version 13 or it is the first time you test ?
I did test a previous version of the series, but I'm not sure if I
tested pmac32 before. So I don't have a known good version.
quoted
[    0.981514] NFS: Registering the id_resolver key type
[    0.981752] Key type id_resolver registered
[    0.981868] Key type id_legacy registered
[    0.995711] Unrecoverable exception 0 at 0 (msr=0)
[    0.996091] Oops: Unrecoverable exception, sig: 6 [#1]
[    0.996314] BE PAGE_SIZE=4K MMU=Hash PowerMac
[    0.996617] Modules linked in:
[    0.996869] CPU: 0 PID: 416 Comm: modprobe Not tainted  
5.0.0-rc2-gcc-7.3.0-00043-g53f2de798792 #342
Comm:modprobe  ==> Something wrong with modules ? I never tested with  
CONFIG_MODULES.
Yep good clue.

cheers
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help