2016-07-15 6:49 GMT+08:00 :
> Wanpeng Li writes:
>
>> 2016-07-15 1:54 GMT+08:00 :
>>> Wanpeng Li writes:
>>>
2016-07-14 1:06 GMT+08:00 :
> Wanpeng Li writes:
>
>> 2016-07-13 1:25 GMT+08:00 :
>>> Konstantin Khlebnikov writes:
>>>
On 11.07.2016 15:12, Xunlei
Wanpeng Li writes:
> 2016-07-15 1:54 GMT+08:00 :
>> Wanpeng Li writes:
>>
>>> 2016-07-14 1:06 GMT+08:00 :
Wanpeng Li writes:
> 2016-07-13 1:25 GMT+08:00 :
>> Konstantin Khlebnikov writes:
>>
>>> On 11.07.2016 15:12, Xunlei Pang wrote:
On 2016/07/11 at 17:5
2016-07-15 1:54 GMT+08:00 :
> Wanpeng Li writes:
>
>> 2016-07-14 1:06 GMT+08:00 :
>>> Wanpeng Li writes:
>>>
2016-07-13 1:25 GMT+08:00 :
> Konstantin Khlebnikov writes:
>
>> On 11.07.2016 15:12, Xunlei Pang wrote:
>>> On 2016/07/11 at 17:54, Wanpeng Li wrote:
Hi
Wanpeng Li writes:
> 2016-07-14 1:06 GMT+08:00 :
>> Wanpeng Li writes:
>>
>>> 2016-07-13 1:25 GMT+08:00 :
Konstantin Khlebnikov writes:
> On 11.07.2016 15:12, Xunlei Pang wrote:
>> On 2016/07/11 at 17:54, Wanpeng Li wrote:
>>> Hi Konstantin, Xunlei,
>>> 2016-07-11 16
2016-07-14 1:06 GMT+08:00 :
> Wanpeng Li writes:
>
>> 2016-07-13 1:25 GMT+08:00 :
>>> Konstantin Khlebnikov writes:
>>>
On 11.07.2016 15:12, Xunlei Pang wrote:
> On 2016/07/11 at 17:54, Wanpeng Li wrote:
>> Hi Konstantin, Xunlei,
>> 2016-07-11 16:42 GMT+08:00 Xunlei Pang :
Wanpeng Li writes:
> 2016-07-13 1:25 GMT+08:00 :
>> Konstantin Khlebnikov writes:
>>
>>> On 11.07.2016 15:12, Xunlei Pang wrote:
On 2016/07/11 at 17:54, Wanpeng Li wrote:
> Hi Konstantin, Xunlei,
> 2016-07-11 16:42 GMT+08:00 Xunlei Pang :
>> On 2016/07/11 at 16:22, Xunlei Pang
2016-07-13 9:58 GMT+08:00 Xunlei Pang :
> On 2016/07/13 at 09:50, Wanpeng Li wrote:
>> 2016-07-13 1:25 GMT+08:00 :
>>> Konstantin Khlebnikov writes:
>>>
On 11.07.2016 15:12, Xunlei Pang wrote:
> On 2016/07/11 at 17:54, Wanpeng Li wrote:
>> Hi Konstantin, Xunlei,
>> 2016-07-11 16:
On 2016/07/13 at 09:50, Wanpeng Li wrote:
> 2016-07-13 1:25 GMT+08:00 :
>> Konstantin Khlebnikov writes:
>>
>>> On 11.07.2016 15:12, Xunlei Pang wrote:
On 2016/07/11 at 17:54, Wanpeng Li wrote:
> Hi Konstantin, Xunlei,
> 2016-07-11 16:42 GMT+08:00 Xunlei Pang :
>> On 2016/07/11 a
2016-07-13 1:25 GMT+08:00 :
> Konstantin Khlebnikov writes:
>
>> On 11.07.2016 15:12, Xunlei Pang wrote:
>>> On 2016/07/11 at 17:54, Wanpeng Li wrote:
Hi Konstantin, Xunlei,
2016-07-11 16:42 GMT+08:00 Xunlei Pang :
> On 2016/07/11 at 16:22, Xunlei Pang wrote:
>> On 2016/07/11 at
Konstantin Khlebnikov writes:
> On 11.07.2016 15:12, Xunlei Pang wrote:
>> On 2016/07/11 at 17:54, Wanpeng Li wrote:
>>> Hi Konstantin, Xunlei,
>>> 2016-07-11 16:42 GMT+08:00 Xunlei Pang :
On 2016/07/11 at 16:22, Xunlei Pang wrote:
> On 2016/07/11 at 15:25, Wanpeng Li wrote:
>> 2016-
On 11.07.2016 15:12, Xunlei Pang wrote:
On 2016/07/11 at 17:54, Wanpeng Li wrote:
Hi Konstantin, Xunlei,
2016-07-11 16:42 GMT+08:00 Xunlei Pang :
On 2016/07/11 at 16:22, Xunlei Pang wrote:
On 2016/07/11 at 15:25, Wanpeng Li wrote:
2016-06-16 20:57 GMT+08:00 Konstantin Khlebnikov :
Hierarchy
On 2016/07/11 at 17:54, Wanpeng Li wrote:
> Hi Konstantin, Xunlei,
> 2016-07-11 16:42 GMT+08:00 Xunlei Pang :
>> On 2016/07/11 at 16:22, Xunlei Pang wrote:
>>> On 2016/07/11 at 15:25, Wanpeng Li wrote:
2016-06-16 20:57 GMT+08:00 Konstantin Khlebnikov
:
> Hierarchy could be already th
Hi Konstantin, Xunlei,
2016-07-11 16:42 GMT+08:00 Xunlei Pang :
> On 2016/07/11 at 16:22, Xunlei Pang wrote:
>> On 2016/07/11 at 15:25, Wanpeng Li wrote:
>>> 2016-06-16 20:57 GMT+08:00 Konstantin Khlebnikov
>>> :
Hierarchy could be already throttled at this point. Throttled next
buddy co
On 2016/07/11 at 16:22, Xunlei Pang wrote:
> On 2016/07/11 at 15:25, Wanpeng Li wrote:
>> 2016-06-16 20:57 GMT+08:00 Konstantin Khlebnikov :
>>> Hierarchy could be already throttled at this point. Throttled next
>>> buddy could trigger null pointer dereference in pick_next_task_fair().
>> There is
On 2016/07/11 at 15:25, Wanpeng Li wrote:
> 2016-06-16 20:57 GMT+08:00 Konstantin Khlebnikov :
>> Hierarchy could be already throttled at this point. Throttled next
>> buddy could trigger null pointer dereference in pick_next_task_fair().
> There is cfs_rq->next check in pick_next_entity(), so how
On 11.07.2016 10:25, Wanpeng Li wrote:
2016-06-16 20:57 GMT+08:00 Konstantin Khlebnikov :
Hierarchy could be already throttled at this point. Throttled next
buddy could trigger null pointer dereference in pick_next_task_fair().
There is cfs_rq->next check in pick_next_entity(), so how can null
2016-06-16 20:57 GMT+08:00 Konstantin Khlebnikov :
> Hierarchy could be already throttled at this point. Throttled next
> buddy could trigger null pointer dereference in pick_next_task_fair().
There is cfs_rq->next check in pick_next_entity(), so how can null
pointer dereference happen?
Regards,
On 16.06.2016 15:57, Konstantin Khlebnikov wrote:
Hierarchy could be already throttled at this point. Throttled next
buddy could trigger null pointer dereference in pick_next_task_fair().
trivial debug in set_next_buddy
@@ -4755,8 +4758,11 @@ static void set_next_buddy(struct sched_entity *se)
Konstantin Khlebnikov writes:
> Hierarchy could be already throttled at this point. Throttled next
> buddy could trigger null pointer dereference in pick_next_task_fair().
>
> Signed-off-by: Konstantin Khlebnikov
Reviewed-by: Ben Segall
> Cc: Stable # v3.2+
> ---
> kernel/sched/fair.c |
Hierarchy could be already throttled at this point. Throttled next
buddy could trigger null pointer dereference in pick_next_task_fair().
Signed-off-by: Konstantin Khlebnikov
Cc: Stable # v3.2+
---
kernel/sched/fair.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git
20 matches
Mail list logo