[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160718135309.GC25380@redhat.com>
Date: Mon, 18 Jul 2016 15:53:10 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Shayan Pooya <shayan@...eve.org>
Cc: Konstantin Khlebnikov <khlebnikov@...dex-team.ru>,
Michal Hocko <mhocko@...nel.org>,
Konstantin Khlebnikov <koct9i@...il.com>,
cgroups mailinglist <cgroups@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org
Subject: Re: bug in memcg oom-killer results in a hung syscall in another
process in the same cgroup
On 07/15, Shayan Pooya wrote:
>
> >> --- x/kernel/sched/core.c
> >> +++ x/kernel/sched/core.c
> >> @@ -2793,8 +2793,11 @@ asmlinkage __visible void schedule_tail(struct task_struct *prev)
> >> balance_callback(rq);
> >> preempt_enable();
> >>
> >> - if (current->set_child_tid)
> >> + if (current->set_child_tid) {
> >> + mem_cgroup_oom_enable();
> >> put_user(task_pid_vnr(current), current->set_child_tid);
> >> + mem_cgroup_oom_disable();
> >> + }
> >> }
> >>
> >> /*
>
> I tried this patch and I still see the same stuck processes (assuming
> that's what you were curious about).
Of course. Because I am stupid. Firtsly, I forgot to include another
change in fault.c. And now I see that change was wrong anyway.
I'll try to make another debugging patch today later, but let me repeat
that it won't fix the real problem anyway.
Thanks, and sorry for wasting your time.
Oleg.
Powered by blists - more mailing lists