From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751732AbcGNWEg (ORCPT ); Thu, 14 Jul 2016 18:04:36 -0400 Received: from mail-pa0-f51.google.com ([209.85.220.51]:34653 "EHLO mail-pa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751210AbcGNWEe (ORCPT ); Thu, 14 Jul 2016 18:04:34 -0400 Date: Thu, 14 Jul 2016 15:04:25 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Tetsuo Handa cc: mpatocka@redhat.com, mhocko@kernel.org, okozina@redhat.com, jmarchan@redhat.com, skozina@redhat.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: System freezes after OOM In-Reply-To: <201607150640.GEB78167.VOFSFHOLMtJOFQ@I-love.SAKURA.ne.jp> Message-ID: References: <20160713145638.GM28723@dhcp22.suse.cz> <201607142001.BJD07258.SMOHFOJVtLFOQF@I-love.SAKURA.ne.jp> <201607150640.GEB78167.VOFSFHOLMtJOFQ@I-love.SAKURA.ne.jp> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 15 Jul 2016, Tetsuo Handa wrote: > Whether the OOM reaper will free some memory no longer matters. Instead, > whether the OOM reaper will let the OOM killer select next OOM victim matters. > > Are you aware that the OOM reaper will let the OOM killer select next OOM > victim (currently by clearing TIF_MEMDIE)? Clearing TIF_MEMDIE in 4.6 occurred > only when OOM reaping succeeded. But we are going to change the OOM reaper > always clear TIF_MEMDIE in 4.8 (or presumably change the OOM killer not to > depend on TIF_MEMDIE) so that the OOM reaper guarantees that the OOM killer > always selects next OOM victim. > That's cute, I'll have to look into those patches.