Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp920300ybe; Fri, 6 Sep 2019 09:13:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqybVo1F2Dt/VvdECthONH0nAxvUkRpI/GLvR3H3/ahywcP8AvTccktVhs/sGXf/iZ9JEObH X-Received: by 2002:a17:90a:8914:: with SMTP id u20mr10051352pjn.111.1567786432064; Fri, 06 Sep 2019 09:13:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567786432; cv=none; d=google.com; s=arc-20160816; b=fWwRxWVthkgfcWkdkNKIQB3Pdy+UrlYBQrnbIRSJxhdpYLqwag+6r9Hfn31dqGCLqW rhSJP+iNX9Eb28rPZpw7n0CtvwBtsEOwKKnfV+27sEf50+b/2nb+8j+6VIMNqEdgjEw0 qGwzXPCTT7QNaKzQ6sV71hrkvwjPF58Qn6zJ0hcF8YQfVNMy7w6Yit2Ff0gAEAjAVwQj VVX+tvSyONbYuANrQg19D5a1m77H6L+ynjeD9QjF/v/md1aR3b173y+2gXpfSokKHL9M ubsPi1sLg7gvqE0urMW4JN+qZqM7lFXZ1ZNPzde6jbJnE+JOLfUpusBSvtVLwAvokZop ZyQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=+Zki5EImiEP41ZLJMM8FzAEoPFCa58GrdxqltqCKR8U=; b=U/EKM6eZI8KA4EX3/wXw5GcO6HJiRewPNzA3Ywb4AEMCd1jIXqmxqMRt23UYdssuVW sphNUGKUQixoDWUHgyr3dciHZIshc0GSUfX09No6RQcu1pyKligfCq+Q4fYIBHWKMEUG QRXhMa+8Ooc6F4YoOqehPEC6r2NmxLyTbZuGWNIbg2Z0Lle+nq9wKRMCG+lvwLh37DSK Hmf4S19NgVJ3ZN5Pk8i9wP1S31GdRCx0CoESajNJc1Sud6AYnmjvO9OGbmmGsn7qVSv4 T1UGkGn9DeVoBnooYVvmEET+KYNvipPmS/w4Dqy8hvkOAFZjabBBr2PrHWBmMBrdidgY c6/w== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u71si4766520pgb.461.2019.09.06.09.13.36; Fri, 06 Sep 2019 09:13:52 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392153AbfIFLCg (ORCPT + 99 others); Fri, 6 Sep 2019 07:02:36 -0400 Received: from mx2.suse.de ([195.135.220.15]:54840 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1731418AbfIFLCg (ORCPT ); Fri, 6 Sep 2019 07:02:36 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 6B409AF2C; Fri, 6 Sep 2019 11:02:34 +0000 (UTC) Date: Fri, 6 Sep 2019 13:02:33 +0200 From: Michal Hocko To: Tetsuo Handa Cc: David Rientjes , linux-mm@kvack.org, Andrew Morton , LKML Subject: Re: [RFC PATCH] mm, oom: disable dump_tasks by default Message-ID: <20190906110233.GE14491@dhcp22.suse.cz> References: <20190903144512.9374-1-mhocko@kernel.org> <20190904054004.GA3838@dhcp22.suse.cz> <12bcade2-4190-5e5e-35c6-7a04485d74b9@i-love.sakura.ne.jp> <20190905140833.GB3838@dhcp22.suse.cz> <20ec856d-0f1e-8903-dbe0-bbc8b7a1847a@i-love.sakura.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20ec856d-0f1e-8903-dbe0-bbc8b7a1847a@i-love.sakura.ne.jp> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 06-09-19 19:46:10, Tetsuo Handa wrote: > On 2019/09/05 23:08, Michal Hocko wrote: > > On Thu 05-09-19 22:39:47, Tetsuo Handa wrote: > > [...] > >> There is nothing that prevents users from enabling oom_dump_tasks by sysctl. > >> But that requires a solution for OOM stalling problem. > > > > You can hardly remove stalling if you are not reducing the amount of > > output or get it into a different context. Whether the later is > > reasonable is another question but you are essentially losing "at the > > OOM event state". > > > > I am not losing "at the OOM event state". Please find "struct oom_task_info" > (for now) embedded into "struct task_struct" which holds "at the OOM event state". > > And my patch moves "printk() from dump_tasks()" from OOM context to WQ context. Workers might be blocked for unbound amount of time and so this information might be printed late. -- Michal Hocko SUSE Labs