From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753021AbaJQP1s (ORCPT ); Fri, 17 Oct 2014 11:27:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20129 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751946AbaJQP1r (ORCPT ); Fri, 17 Oct 2014 11:27:47 -0400 Date: Fri, 17 Oct 2014 17:24:29 +0200 From: Oleg Nesterov To: Cong Wang Cc: Michal Hocko , David Rientjes , "Rafael J. Wysocki" , Tejun Heo , Andrew Morton , LKML Subject: Re: + freezer-check-oom-kill-while-being-frozen.patch added to -mm tree Message-ID: <20141017152429.GA7227@redhat.com> References: <20141016203954.GA26336@redhat.com> <20141016211136.GA27468@redhat.com> <20141016213512.GA28099@redhat.com> <20141016222237.GA30063@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/16, Cong Wang wrote: > > On Thu, Oct 16, 2014 at 3:22 PM, Oleg Nesterov wrote: > > On 10/16, Cong Wang wrote: > >> > >> it will always stay in asleep after schedule()? > > > > Not always. But it will stay asleep in this particular case. > > Hmm, so we still need to wake it up in oom killer: > > if (test_tsk_thread_flag(task, TIF_MEMDIE)) { > if (unlikely(frozen(task))) > wake_up_state(task, TASK_UNINTERRUPTIBLE); > > I will update the patch if Michal doesn't. I think it would be better to simply keep that __thaw_task() in oom_scan_process_thread(). Oleg.