Hi Tejun, On 11/30/2015 11:44 PM, Tejun Heo wrote: > WARNING: CPU: 1 PID: 1 at kernel/cgroup_pids.c:97 pids_cancel.constprop.6+0x31/0x40() > Modules linked in: > CPU: 1 PID: 1 Comm: systemd Not tainted 4.4.0-rc1+ #29 > ... > ffffffff81f65382 ffff88007c043b90 ffffffff81551ffc 0000000000000000 > ffff88007c043bc8 ffffffff810de202 ffff88007a752000 ffff88007a29ab00 > ffff88007c043c80 ffff88007a1d8400 0000000000000001 ffff88007c043bd8 > Call Trace: > [<ffffffff81551ffc>] dump_stack+0x4e/0x82 > [<ffffffff810de202>] warn_slowpath_common+0x82/0xc0 > [<ffffffff810de2fa>] warn_slowpath_null+0x1a/0x20 > [<ffffffff8118e031>] pids_cancel.constprop.6+0x31/0x40 > [<ffffffff8118e0fd>] pids_can_attach+0x6d/0xf0 > [<ffffffff81188a4c>] cgroup_taskset_migrate+0x6c/0x330 > [<ffffffff81188e05>] cgroup_migrate+0xf5/0x190 > [<ffffffff81189016>] cgroup_attach_task+0x176/0x200 > [<ffffffff8118949d>] __cgroup_procs_write+0x2ad/0x460 > [<ffffffff81189684>] cgroup_procs_write+0x14/0x20 > [<ffffffff811854e5>] cgroup_file_write+0x35/0x1c0 > [<ffffffff812e26f1>] kernfs_fop_write+0x141/0x190 > [<ffffffff81265f88>] __vfs_write+0x28/0xe0 > [<ffffffff812666fc>] vfs_write+0xac/0x1a0 > [<ffffffff81267019>] SyS_write+0x49/0xb0 > [<ffffffff81bcef32>] entry_SYSCALL_64_fastpath+0x12/0x76 > > This patch fixes the bug by removing @css parameter from the three > migration methods, ->can_attach, ->cancel_attach() and ->attach() and > updating cgroup_taskset iteration helpers also return the destination > css in addition to the task being migrated. All controllers are > updated accordingly. I was not able to verify if these two patches are fixing it. I don't see the call trace on mainline only when using cgroup/review-xt_cgroup2 review branch. So I ported it to review-xt_croup2 with only a small merge conflict for in netclassid_cgroup.c. No fun though, I still see it. Is there a patch missing? The subject indicates there should be 3 patches. cheers, daniel -- 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
