>[...] >> My script has just detected (and killed) another freezed cgroup. I >> must say that i'm not 100% sure that cgroup was really freezed but it >> has 99% or more memory usage for at least 30 seconds (well, or it has >> 99% memory usage in both two cases the script was checking it). Here >> are stacks of processes inside it before they were killed: >[...] >> pid: 26536 >> stack: >> [<ffffffff81080a45>] refrigerator+0x95/0x160 >> [<ffffffff8106ac2b>] get_signal_to_deliver+0x1cb/0x540 >> [<ffffffff8100188b>] do_signal+0x6b/0x750 >> [<ffffffff81001fc5>] do_notify_resume+0x55/0x80 >> [<ffffffff815cb662>] retint_signal+0x3d/0x7b >> [<ffffffffffffffff>] 0xffffffffffffffff > >[...] > >This task is sitting in the refigerator which means it has been frozen >by the freezer cgroup most probably. I am not familiar with the >implementation but my recollection is that you have to thaw that group >in order the killed process can pass away. >-- >Michal Hocko >SUSE Labs >
Yes, my script is freezing the cgroup before killing processes inside it. Stacks are taken after the freeze, it that problem? azur -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
