From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) by kanga.kvack.org (Postfix) with ESMTP id F14A48E0038 for ; Wed, 9 Jan 2019 07:02:15 -0500 (EST) Received: by mail-ed1-f71.google.com with SMTP id c3so2917978eda.3 for ; Wed, 09 Jan 2019 04:02:15 -0800 (PST) Received: from mx1.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id g15-v6si1194498ejj.234.2019.01.09.04.02.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Jan 2019 04:02:14 -0800 (PST) Date: Wed, 9 Jan 2019 13:02:12 +0100 From: Michal Hocko Subject: Re: [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM Message-ID: <20190109120212.GT31793@dhcp22.suse.cz> References: <20190107143802.16847-1-mhocko@kernel.org> <20190109110328.GS31793@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Tetsuo Handa Cc: linux-mm@kvack.org, Johannes Weiner , Andrew Morton , LKML On Wed 09-01-19 20:34:46, Tetsuo Handa wrote: > On 2019/01/09 20:03, Michal Hocko wrote: > > Tetsuo, > > can you confirm that these two patches are fixing the issue you have > > reported please? > > > > My patch fixes the issue better than your "[PATCH 2/2] memcg: do not > report racy no-eligible OOM tasks" does. OK, so we are stuck again. Hooray! -- Michal Hocko SUSE Labs