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 5ECEFC2D0DC for ; Thu, 26 Dec 2019 05:53:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 35F2D2071E for ; Thu, 26 Dec 2019 05:53:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lca.pw header.i=@lca.pw header.b="Cx17dLra" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726105AbfLZFxa (ORCPT ); Thu, 26 Dec 2019 00:53:30 -0500 Received: from mail-qk1-f193.google.com ([209.85.222.193]:34845 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725263AbfLZFxa (ORCPT ); Thu, 26 Dec 2019 00:53:30 -0500 Received: by mail-qk1-f193.google.com with SMTP id z76so19185984qka.2 for ; Wed, 25 Dec 2019 21:53:29 -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=ocDhrkEib2IZbMXnYTgm3mxljpnoeJ5b/Un4ZkEWnHSCYu1npB2T5g7ECUAxqXqrgf LBVscIj3iv5sasBK8sZX+G2M/P10grX+BsTC/IMmF+DPdD5k6W2tfTxslHWNCx2PblTk UAG3jQpBitVZq3MMGBxmLxoxhex6ihP/PRwVtb84rLOG4LORGBpkg6gevzDTQfCRSWjU wLt6uloSkfIYcLq0wQk48+3r+OXWCm7NVyHxX3khS0mPg9SziviV/HnAsSIjrKnbiI0D doGrW/2T26TrnREYo0AZj4srgD/IoweTg1sHTU4Dd5/nKle954eHM6msmyRvCebh5NUZ IKZA== X-Gm-Message-State: APjAAAUt8GCpKxQwaQgr32x6PiarGgawnW7vKNGFMUCzWHx4bymBqEsW w7iFdeOdrC+GawhEcBid0pNcNw== 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) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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.= 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=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,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 727E6C2D0C0 for ; Thu, 26 Dec 2019 05:53:39 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 42A1B2071E for ; Thu, 26 Dec 2019 05:53:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="tiaqiY1D"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=lca.pw header.i=@lca.pw header.b="Cx17dLra" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 42A1B2071E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lca.pw Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-mediatek-bounces+linux-mediatek=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:In-Reply-To:References:Message-Id: Date:Subject:Mime-Version:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=dy15x1EQpiCgXxbape9B8yUSULafA5mcBnEWHPwb4N0=; b=tiaqiY1DwuUt10 xsu/ZoE2u1aVkLadfkyihI0sR+sgjDRwVuCdsztZpQubelaYAsko6XPvhvsgurGO4MNwUu0+dihgX VIGGpzJ4N+21r+cljdXoRX385kuX0l3F87EllGThZGXXv0vOpgBAgwnYEXy1g/gHVcy2I3N4LkeTk 5BB943JFkv0zRA2kz8gTdut+s2YlIxn/ktEm9Rql65KlicuHhSNs+lSxZd3OY5HPXflQb9hooMYmi tN0iVeNpof3JdgUr69KMI+ESULXFv3OmjDeEre/y+hbNg23uWU/dgIWDv2+fSGWGfro5w+kk5Mpkn I3IIGZV1RatGxvOUrr+Q==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1ikM5a-0003we-8a; Thu, 26 Dec 2019 05:53:38 +0000 Received: from mail-qk1-x743.google.com ([2607:f8b0:4864:20::743]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1ikM5X-0003vz-7P for linux-mediatek@lists.infradead.org; Thu, 26 Dec 2019 05:53:36 +0000 Received: by mail-qk1-x743.google.com with SMTP id 21so18855786qky.4 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=fRjxUp0VQsRegjGLst00NI9lpm30qv47uJt0cQHlUXjZPDMh4kOzXqn6YmMr2AGb0P eqsrVDsTS7c2zeXPk1v7h+398uu9QsEe/DcZUwRUcY6UOqv1siG9WnnAOGLjKjzsW6se 58XD+IX1mZVcaLtIK3TBAUGYil24o4FBETNt1693gmsRwJ6dyYkky3eJv9p7UVegL6xC L0j4kFHnXKwkpzlFAqI2ykvtAkQEOVw/jIad/MCrYpv0nFpXoFzRpHDszm3JWE5Yvpsf 6pqzS1KgyJrGyQJCUV/ccrsOJdMb2vtTpryvmc1XIASeWXDVwglibA0BH/rTG1tKGUD5 g+bg== X-Gm-Message-State: APjAAAXol7eTNRYmKdxKB7lTwLjiTlFQthYIfibIvRuOc2cTmhO4lNjk IcRl3s4kFfKuORRA9dzo0/2Zfg== 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) 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> In-Reply-To: <20191226040114.8123-1-miles.chen@mediatek.com> To: Miles Chen X-Mailer: iPhone Mail (17C54) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191225_215335_314153_3E5F4018 X-CRM114-Status: UNSURE ( 7.51 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-mediatek@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Michal Hocko , wsd_upstream@mediatek.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-mediatek@lists.infradead.org, Andrew Morton Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-mediatek" Errors-To: linux-mediatek-bounces+linux-mediatek=archiver.kernel.org@lists.infradead.org > On Dec 25, 2019, at 11:01 PM, Miles Chen wrote: > > That is what the patch does -- targeting on the memory leakage which causes an OOM kernel panic, so the greatest consumer information helps (the amount of leakage is big enough to cause an OOM kernel panic) > > I've posted the number of real problems since 2019/5 I solved by this approach. The point is in order to make your debugging patch upstream, it has to be general useful. Right now, it feels rather situational for me for the reasons given in the previous emails. _______________________________________________ Linux-mediatek mailing list Linux-mediatek@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-mediatek