On Wed, 3 Oct 2018 08:04:49 +0200
Christophe LEROY wrote:
> Le 03/10/2018 à 07:52, Nicholas Piggin a écrit :
> > On Wed, 3 Oct 2018 07:47:05 +0200
> > Christophe LEROY wrote:
> >
> >> Le 03/10/2018 à 07:30, Nicholas Piggin a écrit :
> >>> On Mon, 1 Oct 2018 12:30:23 + (UTC)
> >>> Chris
Le 03/10/2018 à 07:52, Nicholas Piggin a écrit :
On Wed, 3 Oct 2018 07:47:05 +0200
Christophe LEROY wrote:
Le 03/10/2018 à 07:30, Nicholas Piggin a écrit :
On Mon, 1 Oct 2018 12:30:23 + (UTC)
Christophe Leroy wrote:
This patch activates CONFIG_THREAD_INFO_IN_TASK which
moves the
On Wed, 3 Oct 2018 07:47:05 +0200
Christophe LEROY wrote:
> Le 03/10/2018 à 07:30, Nicholas Piggin a écrit :
> > On Mon, 1 Oct 2018 12:30:23 + (UTC)
> > Christophe Leroy wrote:
> >
> >> This patch activates CONFIG_THREAD_INFO_IN_TASK which
> >> moves the thread_info into task_struct.
> >
Le 03/10/2018 à 07:30, Nicholas Piggin a écrit :
On Mon, 1 Oct 2018 12:30:23 + (UTC)
Christophe Leroy wrote:
This patch activates 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 th
On Mon, 1 Oct 2018 12:30:23 + (UTC)
Christophe Leroy wrote:
> This patch activates 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 stac
This patch activates 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
leak
