Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp980712ybt; Tue, 7 Jul 2020 05:07:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJypyCgdKzZ6nwvaAl41PGbWQGgc41N3fkzHlcsHLRcV5h/mojDdu20KOtrCNLvBSVD3CnXo X-Received: by 2002:a17:906:6446:: with SMTP id l6mr29243168ejn.184.1594123667838; Tue, 07 Jul 2020 05:07:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594123667; cv=none; d=google.com; s=arc-20160816; b=aOwrGi62gsTJ/aX6Slyo4Fjom8QNQeCNLAeewkjFJ+QbiYSv5j4WFTWmoF+j45sno7 jLvjk7E9HPNthXbuPMhJb/fD09ULKzV0nqqYBLUfnXcBvUd5jnfdoKoNcxAJCegMl+io mepgqaKgsQ5aw2d83DGAvrzfwoU6SkHnWeKhN6sIZ/dNrWX6P+tIgcTt8TiAAZAWmYaa pbGK02WRJ2Cu7hvW5BkP1JDYkbL+KATRCsAL2JQL8C1r8c4+1MAW9cX3xq9WdehJKyLW HZ+daSB2G4xS7aFgUDzuKvM+L+5H9iG2oxUf8r8IXP0bEjFtFnJGUde7ld3wFUYancuh 17Rw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=4wU011wHSnWuBlHf2T56JsZw7TsOaUVP+MGeL9UXru4=; b=YBWjp/7wMv2dheN7wT7tLrnGzK8t3XntySKpUqy13ynPygwwQYgqpKWbD6bc5qb5Mc hyksoobdUxSC8v3JW2ExE4L498MU4G5UEWiIFRadKiIspYP8uFVzkAtX0IdAOMXqQSPa P24SWJZP+KJtxlpP6D5WWMPbSMJPQNuhHZStaGEVIlbzWSkI/VnVrpieUoJnGP7t1M0a qt7IgUoV9OMPH6SYpuXtqBBAYSGBDL4sLQdi+R/RfBAXSRqqEmrin1wlwdvvOgXHSSNK ZHgxq5GhqXRVdnfNPpFR1eJna8nPFlLQc9grSuLdd/E8HVNeLbW+WHbLn5OUyMXg7jar amCQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k18si640724eds.136.2020.07.07.05.07.24; Tue, 07 Jul 2020 05:07:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727789AbgGGMGZ (ORCPT + 99 others); Tue, 7 Jul 2020 08:06:25 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:45001 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726805AbgGGMGY (ORCPT ); Tue, 7 Jul 2020 08:06:24 -0400 Received: by mail-wr1-f68.google.com with SMTP id b6so44850642wrs.11 for ; Tue, 07 Jul 2020 05:06:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=4wU011wHSnWuBlHf2T56JsZw7TsOaUVP+MGeL9UXru4=; b=DTtETGPO6OAljirHWkJwk255j8riYZZowzArTTsxtZ/Ay980al4YuYorqd2/WvJVO3 maSAQ/hPQrTDKGhc6/8SqKFSJfMyA1HkqB88WaYSepK2mFeu+rRnGCI021B+wr7GgknJ b1YRJOBvyZE3SJPB8oCOaJGiNnZelahx3W8FAW/OClXqmxpZYkcXFQjrgTmAcKHNg18L DVgMBTftvqFDi0pxY7z736ckuaG3RgZUxdk6TVg5343fEx/TvwCAia+qth2e06y/ecba sFmYG/fXlniOtdMRVt8VyyouhvFBxw94HL41vzlGwar0VHR59LQUMspqN8e8IZHiSJd2 Xl1w== X-Gm-Message-State: AOAM532sHnIS5mt4kByTnBmjVh2lOSrcq5U4Zk9TVwlPuuJKqFkFUQl1 f9sZO4EIvNIURzT5Ld76wmJqjRfA X-Received: by 2002:a5d:458a:: with SMTP id p10mr52821643wrq.184.1594123582099; Tue, 07 Jul 2020 05:06:22 -0700 (PDT) Received: from localhost (ip-37-188-179-51.eurotel.cz. [37.188.179.51]) by smtp.gmail.com with ESMTPSA id n14sm722767wro.81.2020.07.07.05.06.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Jul 2020 05:06:21 -0700 (PDT) Date: Tue, 7 Jul 2020 14:06:19 +0200 From: Michal Hocko To: Qian Cai Cc: Feng Tang , kernel test robot , Andrew Morton , Johannes Weiner , Matthew Wilcox , Mel Gorman , Kees Cook , Luis Chamberlain , Iurii Zaikin , andi.kleen@intel.com, tim.c.chen@intel.com, dave.hansen@intel.com, ying.huang@intel.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, lkp@lists.01.org Subject: Re: [mm] 4e2c82a409: ltp.overcommit_memory01.fail Message-ID: <20200707120619.GO5913@dhcp22.suse.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 07-07-20 07:43:48, Qian Cai wrote: > > > > On Jul 7, 2020, at 6:28 AM, Michal Hocko wrote: > > > > Would you have any examples? Because I find this highly unlikely. > > OVERCOMMIT_NEVER only works when virtual memory is not largerly > > overcommited wrt to real memory demand. And that tends to be more of > > an exception rather than a rule. "Modern" userspace (whatever that > > means) tends to be really hungry with virtual memory which is only used > > very sparsely. > > > > I would argue that either somebody is running an "OVERCOMMIT_NEVER" > > friendly SW and this is a permanent setting or this is not used at all. > > At least this is my experience. > > > > So I strongly suspect that LTP test failure is not something we should > > really lose sleep over. It would be nice to find a way to flush existing > > batches but I would rather see a real workload that would suffer from > > this imprecision. > > I hear you many times that you really don’t care about those use > cases unless you hear exactly people are using in your world. > > For example, when you said LTP oom tests are totally artificial last > time and how less you care about if they are failing, and I could only > enjoy their efficiencies to find many issues like race conditions > and bad error accumulation handling etc that your “real world use > cases” are going to take ages or no way to flag them. Yes, they are effective at hitting corner cases and that is fine. I am not dismissing their usefulness. I have tried to explain that many times but let me try again. Seeing a corner case and think about a potential fix is one thing. On the other hand it is not really ideal to treat such a failure a hard regression and consider otherwise useful functionality/improvement to be reverted without a proper cost benefit analysis. Sure having corner cases is not really nice but really, look at this example again. Overcommit setting is a global thing, it is hard to change it during runtime nilly willy. Because that might have really detrimental side effects on all workloads running. So it is quite reasonable to expect that this is either early after the boot or when the system is in quiescent state when almost nothing but very core services are running and likelihood that the mode of operation changes. > There are just too many valid use cases in this wild world. The > difference is that I admit that I don’t know or even aware all the > use cases, and I don’t believe you do as well. Me neither and I am not claiming that. All I am saying is that a real risk of a regression is reasonably low that I wouldn't lose sleep over that. It is perfectly fine to address this pro-actively if the fix is reasonably maintainable. I was mostly reacting to your pushing for a revert solely based on LTP results. LTP is a very useful tool to raise awareness of potential problems but you shouldn't really follow those results just blindly. > If a patchset broke the existing behaviors that written exactly in > the spec, it is then someone has to prove its innocent. For example, > if nobody is going to rely on something like this now and future, and > then fix the spec and explain exactly nobody should be rely upon. I am all for clarifications in the documentation. -- Michal Hocko SUSE Labs