lkml.org 
[lkml]   [2013]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [patch 0/7] improve memcg oom killer robustness v2
    Date
    From
    >[...]
    >> 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


    \
     
     \ /
      Last update: 2013-09-04 14:41    [W:5.048 / U:0.000 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site