Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3261696imm; Sun, 3 Jun 2018 23:54:32 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIakwPTBDRnFVe84v8b22G8pslSjDQiHZq/340RMWQ2k1hmH1WKJIPdL4LsESj6tDvwkUGV X-Received: by 2002:a62:1e02:: with SMTP id e2-v6mr20210266pfe.212.1528095272877; Sun, 03 Jun 2018 23:54:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528095272; cv=none; d=google.com; s=arc-20160816; b=nCYoRnueF5mYJepshM5C6plWvHHdGPnEzfTlenJ9bCU6kcXzgpf/36VNYJfKuJNLac 8NaGJqocvZVeIetHsUR/GAS+IVbI5Osgqsk3Qu7agC3UqfSCwF8G+466KoQ9L/2ms0jS zMyWiaT90v7ek+tNNh1VR7GvM5BjEurMykFaKHLiJwFxCYiXvZxd0IGAEDqTkvW5IBVE ENamcr/JrUA89OcmxbqYd2RqDjSQI8R4/iH4eLAiZ6JSLnqQjbIEFpZNTxU/lhOuU9fB X4996yaqHhhp8b8aOpEn1gBe5o3l6y4IcC4IWGfHh9YIBischJ1kuZ5JZy2Wy3dyHDf9 bENA== 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:arc-authentication-results; bh=MVCmLCFB5+ULCNvMNix7IZuJNtyVYHcfNWiPC+0blHU=; b=P7fL5O7Undqmt0tZG5zfhvGlKIkKk+81kzfU/x3SudIMlGWo971l44t9am+9SRfeqZ 7TOGW0x716ujeXgsBxlcB171upwWQKKWUY2eyDpaGemi28OZ/wtC2MjXVib/kcPU9aEw iwWUU/NH5mWSt+2NCn9X7jychnj42YBLeOQnR4k0Gf1FuRQGtm9Cnha/RI4oPplbcUlh HrhwY9hQLloJQiIiYLo2g4wseXRyxxrNo+m2PfMX8dZNd+c7yG+pZ+b1FXJX/fK7fxdh aB68GcKrTPRsHJb3StR1PT4KfI90zbyEo9ZZB4vA3mPA/5anTu8INa1FPQtG2NqvYI/Q gWRw== 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 r59-v6si44882288plb.314.2018.06.03.23.54.18; Sun, 03 Jun 2018 23:54:32 -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 S1751820AbeFDGwm (ORCPT + 99 others); Mon, 4 Jun 2018 02:52:42 -0400 Received: from mx2.suse.de ([195.135.220.15]:53778 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751047AbeFDGwl (ORCPT ); Mon, 4 Jun 2018 02:52:41 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 70F22AE01; Mon, 4 Jun 2018 06:52:40 +0000 (UTC) Date: Mon, 4 Jun 2018 08:52:38 +0200 From: Michal Hocko To: ufo19890607@gmail.com Cc: akpm@linux-foundation.org, rientjes@google.com, kirill.shutemov@linux.intel.com, aarcange@redhat.com, penguin-kernel@I-love.SAKURA.ne.jp, guro@fb.com, yang.s@alibaba-inc.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, yuzhoujian Subject: Re: [PATCH v7 2/2] Refactor part of the oom report in dump_header Message-ID: <20180604065238.GE19202@dhcp22.suse.cz> References: <1527940734-35161-1-git-send-email-ufo19890607@gmail.com> <1527940734-35161-2-git-send-email-ufo19890607@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1527940734-35161-2-git-send-email-ufo19890607@gmail.com> User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat 02-06-18 19:58:52, ufo19890607@gmail.com wrote: > From: yuzhoujian > > The dump_header does not print the memcg's name when the system > oom happened, so users cannot locate the certain container which > contains the task that has been killed by the oom killer. > > I follow the advices of David Rientjes and Michal Hocko, and refactor > part of the oom report in a backwards compatible way. After this patch, > users can get the memcg's path from the oom report and check the certain > container more quickly. I have earlier suggested that you split this into two parts. One to add the missing information and the later to convert it to a single printk output. Reducing the overhead from PATH_MAX to NAME_MAX is a good step but it still really begs an example why we really insist on a single printk and that should be in its own changelog. Sorry if that was not clear previously. -- Michal Hocko SUSE Labs