Received: by 10.213.65.68 with SMTP id h4csp909572imn; Wed, 4 Apr 2018 09:14:50 -0700 (PDT) X-Google-Smtp-Source: AIpwx49n6hmRqdBnPBpOFniUg/oRGxwyDyEEbVcGfIlKHBWBef7MowVGa3/sn5fJtrGWwsuF61es X-Received: by 10.101.98.145 with SMTP id f17mr12025462pgv.398.1522858490474; Wed, 04 Apr 2018 09:14:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522858490; cv=none; d=google.com; s=arc-20160816; b=aYrwlhgdM+aPGLsJT5cNKKGfZlONU1hNHTR06FnjhQ7lh6Md9NAscOrvas/TTSZyNg 8YqBPyNb6BYsD9jVj3HEVjtIFo91ZhSBoYj99bwY6tL91EsUdl+8ZNnxhYlGACfkI2qM 8izjtWzzHqVMXV4jCaqy6u+8t4TAkY/MBpPn0UOk8jSYCJ41xmZ5RVCYHBHyjQy3kcIS qkzwpdbsrDkU+ZY2NE2RJwbnh6gZnD0N7ErCKKZIlTF6i2/3fWO24d4/BDHXlFZCBHDR Nbe3VoOEsdzlQE9rItBzCmVa+zvKOUxs5o+4MaAXQOPFAeUIsOrTbuOWDKzSxh7bCA64 RTgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dmarc-filter:arc-authentication-results; bh=F9J/Jj+H59foKuxtfC/HvUKSjqhy77uziIRCR3a9R/M=; b=VNgNJxH3Lg/R/t1yQch+9gbN8iaqx0bVQagW9UBbeAU+89ORNt7LIDO73x5pSJv8E3 joBjD0C8lJVukzE8empMsjsnVQ3EnUMS4a0iJ5AHilp55rL5KLHqn0u51/k/z3AXPa60 r/9yyhJb9DEk1yaJQ8cjFH43MW2DtWF9RcV3Ude5lXmy8LkrdXpZsUBelevSRNZyppV+ EERzb0EPvTJzPVUz+BrbAE3kNlOgGZuOj6li6Ve6NtrXsqUy5R7ZtO7Jmhm5kulhspYy /PfrVweIuxwDsDU7K9HzsBjLP/2PFOt3GHhhlZn3EJYqipbkvIZAIlFxT4ZgBkp7r5dy QOyw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t14si573392pfg.225.2018.04.04.09.14.36; Wed, 04 Apr 2018 09:14:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752021AbeDDQNa (ORCPT + 99 others); Wed, 4 Apr 2018 12:13:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:52350 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751606AbeDDQN3 (ORCPT ); Wed, 4 Apr 2018 12:13:29 -0400 Received: from gandalf.local.home (cpe-66-24-56-78.stny.res.rr.com [66.24.56.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B56222133F; Wed, 4 Apr 2018 16:13:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B56222133F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Wed, 4 Apr 2018 12:13:26 -0400 From: Steven Rostedt To: Joel Fernandes Cc: LKML , Michal Hocko , Zhaoyang Huang , Ingo Molnar , kernel-patch-test@lists.linaro.org, Andrew Morton , "open list:MEMORY MANAGEMENT" , Vlastimil Babka Subject: Re: [PATCH] ring-buffer: Add set/clear_current_oom_origin() during allocations Message-ID: <20180404121326.6eca4fa3@gandalf.local.home> In-Reply-To: References: <20180404115310.6c69e7b9@gandalf.local.home> <20180404120002.6561a5bc@gandalf.local.home> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 4 Apr 2018 09:03:47 -0700 Joel Fernandes wrote: > > for the tests. Note, without this, I tried to allocate all memory > > (bisecting it with allocations that failed and allocations that > > succeeded), and couldn't trigger an OOM :-/ > > I guess you need to have something *else* other than the write to > buffer_size_kb doing the GFP_KERNEL allocations but unfortunately gets > OOM killed? Yeah, for some reason, my test box seems to always have something doing that, because I trigger an OOM about 2 out of every 3 tries. Here's the tasks that trigger it: lvmetad, crond, systemd-journal, abrt-dump-journ, chronyd, I guess my system is rather busy even when idle :-/ > > Also, I agree with the new patch and its nice idea to do that. Thanks, want to give it a test too? -- Steve