> synchronize_rcu() is a block operation and can keep us waiting for
> a long period, so instead it's possible that usage never goes down
> to 0 and we are in a dead loop.
Ok, I didn't think of that. Tracing shows that the function keeps
looping. The last lines repeat indefinitely.
kworker/2:0-6747 [002] .... 926.354954:
mem_cgroup_reparent_charges: usage: 0
kworker/4:1-542 [004] .... 926.366555:
mem_cgroup_reparent_charges: usage: 0
##### CPU 6 buffer started ####
kworker/6:1-2553 [006] .... 926.377376:
mem_cgroup_reparent_charges: usage: 0
##### CPU 0 buffer started ####
kworker/0:4-7306 [000] .... 926.399285:
mem_cgroup_reparent_charges: usage: 0
kworker/0:6-7308 [000] .... 926.411155:
mem_cgroup_reparent_charges: usage: 0
kworker/0:7-7309 [000] .... 926.420248:
mem_cgroup_reparent_charges: usage: 0
kworker/6:2-7304 [006] .... 926.432144:
mem_cgroup_reparent_charges: usage: 0
##### CPU 7 buffer started ####
kworker/7:2-7303 [007] .... 926.438061:
mem_cgroup_reparent_charges: usage: 0
kworker/2:2-2813 [002] .... 926.451030:
mem_cgroup_reparent_charges: usage: 0
kworker/0:8-7310 [000] .... 926.466091:
mem_cgroup_reparent_charges: usage: 0
kworker/7:0-240 [007] .... 926.478073:
mem_cgroup_reparent_charges: usage: 0
kworker/4:0-225 [004] .... 926.485006:
mem_cgroup_reparent_charges: usage: 0
kworker/2:3-7311 [002] .... 926.497057:
mem_cgroup_reparent_charges: usage: 0
##### CPU 1 buffer started ####
kworker/1:3-7313 [001] .... 926.502987:
mem_cgroup_reparent_charges: usage: 0
kworker/4:3-7315 [004] .... 926.509086:
mem_cgroup_reparent_charges: usage: 0
kworker/1:4-7317 [001] .... 926.518786:
mem_cgroup_reparent_charges: usage: 0
kworker/2:4-7316 [002] .... 926.524988:
mem_cgroup_reparent_charges: usage: 0
kworker/2:5-7320 [002] .... 926.538006:
mem_cgroup_reparent_charges: usage: 0
##### CPU 34 buffer started ####
kworker/34:1-1453 [034] .... 926.569158:
mem_cgroup_reparent_charges: usage: 0
##### CPU 3 buffer started ####
kworker/3:5-7605 [003] .... 987.403711:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.406709:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.409708:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.412706:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.415705:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.418703:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.424688:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.427700:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.430698:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.433697:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.436696:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.439694:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.442693:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.445692:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.448691:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.451689:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.454688:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.457686:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.460685:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.463684:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.469668:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.472680:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.475678:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.478677:
mem_cgroup_reparent_charges: usage: 1568768
kworker/3:5-7605 [003] .... 987.481675:
mem_cgroup_reparent_charges: usage: 1568768
--
To unsubscribe from this list: send the line "unsubscribe cgroups" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
