On 05/16/2014 11:35 AM, Oleg Nesterov wrote:
> On 05/16, Sasha Levin wrote:
>>
>> On 04/13/2014 03:56 PM, Oleg Nesterov wrote:
>>> 1. Remove CLONE_KERNEL, it has no users and it is dangerous.
>>>
>>>The (old) comment says "List of flags we want to share for kernel
>>>threads" but this is no
On 05/16, Sasha Levin wrote:
>
> On 04/13/2014 03:56 PM, Oleg Nesterov wrote:
> > 1. Remove CLONE_KERNEL, it has no users and it is dangerous.
> >
> >The (old) comment says "List of flags we want to share for kernel
> >threads" but this is not true, we do not want to share ->sighand by
> >
On 04/13/2014 03:56 PM, Oleg Nesterov wrote:
> 1. Remove CLONE_KERNEL, it has no users and it is dangerous.
>
>The (old) comment says "List of flags we want to share for kernel
>threads" but this is not true, we do not want to share ->sighand by
>default. This flag can only be used if
On Sun, 13 Apr 2014 21:56:17 +0200
Oleg Nesterov wrote:
> 1. Remove CLONE_KERNEL, it has no users and it is dangerous.
>
>The (old) comment says "List of flags we want to share for kernel
>threads" but this is not true, we do not want to share ->sighand by
>default. This flag can onl
On Sun, Apr 13, 2014 at 09:56:17PM +0200, Oleg Nesterov wrote:
> 1. Remove CLONE_KERNEL, it has no users and it is dangerous.
>
>The (old) comment says "List of flags we want to share for kernel
>threads" but this is not true, we do not want to share ->sighand by
>default. This flag ca
1. Remove CLONE_KERNEL, it has no users and it is dangerous.
The (old) comment says "List of flags we want to share for kernel
threads" but this is not true, we do not want to share ->sighand by
default. This flag can only be used if the caller is sure that both
parent/child will never
6 matches
Mail list logo