From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 41713C2D0C0 for ; Thu, 26 Dec 2019 05:53:32 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id C54172071E for ; Thu, 26 Dec 2019 05:53:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lca.pw header.i=@lca.pw header.b="Cx17dLra" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C54172071E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lca.pw Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 2571B8E0005; Thu, 26 Dec 2019 00:53:31 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 207458E0001; Thu, 26 Dec 2019 00:53:31 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 0F5C48E0005; Thu, 26 Dec 2019 00:53:31 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0027.hostedemail.com [216.40.44.27]) by kanga.kvack.org (Postfix) with ESMTP id EEA868E0001 for ; Thu, 26 Dec 2019 00:53:30 -0500 (EST) Received: from smtpin04.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with SMTP id 99575181AEF00 for ; Thu, 26 Dec 2019 05:53:30 +0000 (UTC) X-FDA: 76306225380.04.brass08_58cb729c97f5b X-HE-Tag: brass08_58cb729c97f5b X-Filterd-Recvd-Size: 3700 Received: from mail-qk1-f193.google.com (mail-qk1-f193.google.com [209.85.222.193]) by imf18.hostedemail.com (Postfix) with ESMTP for ; Thu, 26 Dec 2019 05:53:30 +0000 (UTC) Received: by mail-qk1-f193.google.com with SMTP id t129so18806074qke.10 for ; Wed, 25 Dec 2019 21:53:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lca.pw; s=google; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=cLzbJhpD5Hwr6N5MywLf3Xs4c3eeLRB2SD3vQXIQzSw=; b=Cx17dLrafYJa5xPSv3lVV3wzk31qC+KuZ6fLVcFnXa4R/jDr945lUBLfgMMNqesPO2 bbPvceUrbeuHpRJbs9gPFRRoCA3Oa7L32NITAvVcWQxV3lOjAmjxzcCijmWuHrVv/bDW PN5o0PsuX/Z0BmPbo7U3DJ8oJwNvMZ5E2vCiRJTRLIakHip1+ffnlDToeZArfb2D8UZY HKUa3kDwmYWMMpP+SaXltEIN/aMU8P7De+gA/OYTrJ6JdnYzGhIRTyk+Xe74Qy7usL7o XcgSwW77eQcilqJDF4qeTna4Rea8G6Q/hH3MQTg6q0KnSj3njHUUzKf+GVDYo9vuGQ/M HCxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=cLzbJhpD5Hwr6N5MywLf3Xs4c3eeLRB2SD3vQXIQzSw=; b=IRnvLRrALLq0CARuFE/GE1FHM4HjUuAEDVFyHijz7sByI3WSS4R1JhT1m6zOucpwp5 C1fNYg7hlCkLDEVTAkW1yH1kHfVaIrtk3+U4Rb6BEPJcFT/irOJot2tOt0T8h7xTWVuj NPwmIclqWjGOkfxoRvw4ijE02kYlVu6z66JRhQZsuzWHneL/vCInmMHPwhoU3FNGzszP bRDk2Mt2Q/uzuDf6u1Q8J2FhNdqtX1/Ms2O+H9NAWXGUBrb+cBo9obVuLbzdmsDiKrRe d+oEv3xBnEHI4gLCP35ttTNK+22oNP62GAWMl02wWpHKl4IF06U2BOWKAfIfDta4K7tf zSdw== X-Gm-Message-State: APjAAAUpmJFXiFL2TohHguqoe1adMMcgiJBqI5Br/rn5Mjmt3OgWky31 NMsqNuZQry2XNNAtGvIdTypywaOqn0A= X-Google-Smtp-Source: APXvYqzdbAALcUwCJ//wHxNu4rEzRWBsEQ9+zVEIJE8/RNPfGM5mfTkwmvfYkpkDZDHTnScUlnklKQ== X-Received: by 2002:ae9:c018:: with SMTP id u24mr37176052qkk.339.1577339609314; Wed, 25 Dec 2019 21:53:29 -0800 (PST) Received: from [192.168.1.183] (pool-71-184-117-43.bstnma.fios.verizon.net. [71.184.117.43]) by smtp.gmail.com with ESMTPSA id t3sm9253977qtc.8.2019.12.25.21.53.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 25 Dec 2019 21:53:28 -0800 (PST) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Qian Cai Mime-Version: 1.0 (1.0) Subject: Re: [PATCH] mm/page_owner: print largest memory consumer when OOM panic occurs Date: Thu, 26 Dec 2019 00:53:27 -0500 Message-Id: <95CD23C9-D10D-4E6A-BF53-A4C1A4DB281A@lca.pw> References: <20191226040114.8123-1-miles.chen@mediatek.com> Cc: Andrew Morton , Michal Hocko , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com In-Reply-To: <20191226040114.8123-1-miles.chen@mediatek.com> To: Miles Chen X-Mailer: iPhone Mail (17C54) X-Bogosity: Ham, tests=bogofilter, spamicity=0.130607, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: > On Dec 25, 2019, at 11:01 PM, Miles Chen wrote: >=20 > That is what the patch does -- targeting on the memory leakage which cause= s an OOM kernel panic, so the greatest consumer information helps (the amoun= t of leakage is big enough to cause an OOM kernel panic) >=20 > I've posted the number of real problems since 2019/5 I solved by this appr= oach. The point is in order to make your debugging patch upstream, it has to be ge= neral useful. Right now, it feels rather situational for me for the reasons g= iven in the previous emails.=