From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752419AbaAPJc0 (ORCPT ); Thu, 16 Jan 2014 04:32:26 -0500 Received: from cantor2.suse.de ([195.135.220.15]:37118 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751591AbaAPJcX (ORCPT ); Thu, 16 Jan 2014 04:32:23 -0500 Date: Thu, 16 Jan 2014 10:32:20 +0100 From: Michal Hocko To: David Rientjes Cc: Johannes Weiner , Andrew Morton , KAMEZAWA Hiroyuki , linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, "Eric W. Biederman" Subject: Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves Message-ID: <20140116093220.GC28157@dhcp22.suse.cz> References: <20140107162503.f751e880410f61a109cdcc2b@linux-foundation.org> <20140109144757.e95616b4280c049b22743a15@linux-foundation.org> <20140109161246.57ea590f00ea5b61fdbf5f11@linux-foundation.org> <20140110221432.GD6963@cmpxchg.org> <20140115143449.GN8782@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 15-01-14 13:23:10, David Rientjes wrote: > On Wed, 15 Jan 2014, Michal Hocko wrote: [...] > > Which depends on yours only to revert your part. I plan to repost it but > > that still doesn't mean it will get merged because Johannes still has > > some argumnets against. I would like to start the discussion again > > because now we are so deep in circles that it is hard to come up with a > > reasonable outcome. It is still hard to e.g. agree on an actual fix > > for a real problem https://lkml.org/lkml/2013/12/12/129. > > > > This is concerning because it's merged in -mm without being tested by Eric > and is marked for stable while violating the stable kernel rules criteria. Are you questioning the patch fixes the described issue? Please note that the exit_robust_list and PF_EXITING as a culprit has been identified by Eric. Of course I would prefer if it was tested by anybody who can reproduce it. -- Michal Hocko SUSE Labs