[lkml]   [2011]   [May]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] sched: rt_rq runtime leakage bug fix
On 2011-5-12 18:12, Peter Zijlstra wrote:
> it would be nice to know why the , operator version
> doesn't work though, since that looks to be the more conventional way to
> write it.

I did some investigation, it looks that,

1 #define for_each_rt_rq(rt_rq, iter, rq) \
2 for (iter = list_entry_rcu(, typeof(*iter), list), \
3 rt_rq = iter->rt_rq[cpu_of(rq)]; &iter->list != &task_groups; \
4 iter = list_entry_rcu(iter->, typeof(*iter), list), \
5 rt_rq = iter->rt_rq[cpu_of(rq)])

in for loop, when task_groups (as sentinel node of the doubly linked circular list) is reached after the final iteration, a fake iter (of struct task_group *) is calculated at line 4 via container_of(&task_groups, struct task_group, list). By "fake", as we know, it is just an address, with &iter->list == &task_groups, but not pointing to a true struct task_group object. Accessing other members of fake iter might be the cause of page fault.

In my JS22 blade, cpu_of(rq)=1 and fake iter->rt_rq happens to be 0x100000000, value of another global variable near task_groups. Kernel tries to take it plus 8 as address, to retrieve iter->rt_rq[1]. and then page fault happens at address 0x100000008.

 \ /
  Last update: 2011-05-14 07:51    [W:0.104 / U:4.804 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site