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=-8.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 4A1FAC433E0 for ; Wed, 10 Mar 2021 07:42:52 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id D4E8B64FDE for ; Wed, 10 Mar 2021 07:42:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D4E8B64FDE Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 288C48D017C; Wed, 10 Mar 2021 02:42:51 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 238E08D0148; Wed, 10 Mar 2021 02:42:51 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 0DC2B8D017C; Wed, 10 Mar 2021 02:42:51 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0137.hostedemail.com [216.40.44.137]) by kanga.kvack.org (Postfix) with ESMTP id E485C8D0148 for ; Wed, 10 Mar 2021 02:42:50 -0500 (EST) Received: from smtpin21.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id A24F0181AF5D8 for ; Wed, 10 Mar 2021 07:42:50 +0000 (UTC) X-FDA: 77903172900.21.36B76A8 Received: from mail-pf1-f172.google.com (mail-pf1-f172.google.com [209.85.210.172]) by imf04.hostedemail.com (Postfix) with ESMTP id 491BD3C2 for ; Wed, 10 Mar 2021 07:42:49 +0000 (UTC) Received: by mail-pf1-f172.google.com with SMTP id y67so11535163pfb.2 for ; Tue, 09 Mar 2021 23:42:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=PgzuC8/TNXUF5UZqdDTCIRg3y35yfyPd03qqWgWTsJ4=; b=B3az+5aKkQv8oKsx41T73ASQ/XRUUv/PD8x3u6627vmTMF9pgVDTDNCtihfrqX8GLp 9UZ8xWnW4M47fsyZG3HbPOJ35IpAlSQjREOb+IzE4MglvzO2ACMgQ+YbramzEmSYSkBk OOi2OvLF2EMt8uDnol4CyLe3JZ/xACiZTcegeOB5kEFVg11hXo3J51dBjGtkHO4ngZxD zkoY1mSLbkhW3mDa7u9VnB4+a9HIdUhqzmZt/6VQL2T3EEu4ACY7k27cL14kEHosDWz6 hmJssGQnKr7A2XXYVr8O2l003iCimXuE9PKq0cZjCL8j3tZ7hlx8RsVQXEIv8OETPZc6 U16A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=PgzuC8/TNXUF5UZqdDTCIRg3y35yfyPd03qqWgWTsJ4=; b=jnTgcWRq1N4tFvjwlR22sPwE1hIuQFnVKYiulygSS4mImCZk6OvTHIQwnClrMNcAns 8fOd9Zi68eMCysakIUZZYF8q5iU3gPwBOGUSMDQOtNIvagm15WYRNDo+ycFTxqV8aWBl uA5TsvlQzXfe2r92zmgS2Cuu/cq8kx6KghbL5hLbo/CT1X8VXs8/hpLDqFM8HTdFgT7J LBm/Em7y+LIEnAJSupZi+3t/hk8EWsIlvhL2+BTnDv1Am1YJ5HNMWQ1fh2hWIE3Tou0k ci/Vu8DFRVow7NklqrUyy5wDY9TH+ct2PVfVbugmv4UI4Nci88TZme9uIft45W/NFzIu KwRg== X-Gm-Message-State: AOAM5325wOd7E1IgzMhyaClNyn/+JBfjCU7VUCIXc6HJHd4RJNazTzgC 8fGeGJzsTKIT0Nj+6crHI68= X-Google-Smtp-Source: ABdhPJx+aIT0R3oWBbHjfi73oOJplCSsgFHW6973ObD5KeT3MnmeKXtzBeRDUjYBaqJddxjLUxwqwg== X-Received: by 2002:a63:8f5d:: with SMTP id r29mr1657909pgn.353.1615362168930; Tue, 09 Mar 2021 23:42:48 -0800 (PST) Received: from google.com ([2620:15c:211:201:f896:d6be:86d4:a59b]) by smtp.gmail.com with ESMTPSA id r184sm15608540pfc.107.2021.03.09.23.42.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 09 Mar 2021 23:42:48 -0800 (PST) Date: Tue, 9 Mar 2021 23:42:46 -0800 From: Minchan Kim To: Michal Hocko Cc: Andrew Morton , linux-mm , LKML , John Dias , David Hildenbrand , Jason Baron Subject: Re: [PATCH v2] mm: page_alloc: dump migrate-failed pages Message-ID: References: <20210308202047.1903802-1-minchan@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 491BD3C2 X-Stat-Signature: 9gxrs7u9ff1an6ani9urqhqu5wmg8aqz Received-SPF: none (gmail.com>: No applicable sender policy available) receiver=imf04; identity=mailfrom; envelope-from=""; helo=mail-pf1-f172.google.com; client-ip=209.85.210.172 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1615362169-47920 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Mar 09, 2021 at 08:15:41AM -0800, Minchan Kim wrote: < snip > > > [...] > > > +void dump_migrate_failure_pages(struct list_head *page_list) > > > +{ > > > + DEFINE_DYNAMIC_DEBUG_METADATA(descriptor, > > > + "migrate failure"); > > > + if (DYNAMIC_DEBUG_BRANCH(descriptor) && > > > + alloc_contig_ratelimit()) { > > > + struct page *page; > > > + > > > + WARN(1, "failed callstack"); > > > + list_for_each_entry(page, page_list, lru) > > > + dump_page(page, "migration failure"); > > > + } > > > > Apart from the above, do we have to warn for something that is a > > debugging aid? A similar concern wrt dump_page which uses pr_warn and > > Make sense. > > > page owner is using even pr_alert. > > Would it make sense to add a loglevel parameter both into __dump_page > > and dump_page_owner? > > Let me try it. I looked though them and made first draft to clean them up. It's bigger than my initial expectaion because there are many callsites to use dump_page and stack_trace_print inconsistent loglevel. Since it's not a specific problem for this work, I'd like to deal with it as separate patchset since I don't want to be stuck on here for my initial goal. FYI, Subject: [RFC 0/5] make dump_page aware of loglevel - Forked from [1] dump_page uses __dump_page and dump_page_owner internally to print various information. However, their printk loglevel are inconsistent in that __dump_page: KERN_WARNING __dump_page_owner: KERN_ALERT stack_trace_print: KERN_DEFAULT To make them consistent from dump_page, this patch introduces pr_loglevel in printk and make the utility functions aware of loglevel. Finally, last patch changes dump_page to support loglevel to make the printing level consistent. [1] https://lore.kernel.org/linux-mm/YEdAw6gnp9XxoWUQ@dhcp22.suse.cz/ Minchan Kim (5): mm: introduce pr_loglevel for __dump_[page]_owner stacktrace: stack_trace_print aware of loglevel mm: page_owner: dump_page_owner aware of loglevel mm: debug: __dump_page aware of loglevel mm: debug: dump_page aware of loglevel drivers/md/dm-bufio.c | 2 +- drivers/virtio/virtio_mem.c | 2 +- fs/btrfs/ref-verify.c | 2 +- fs/fuse/dev.c | 2 +- include/linux/mmdebug.h | 10 ++++++---- include/linux/page_owner.h | 8 ++++---- include/linux/printk.h | 12 +++++++++++ include/linux/stacktrace.h | 4 ++-- kernel/backtracetest.c | 2 +- kernel/dma/debug.c | 3 ++- kernel/kcsan/report.c | 7 ++++--- kernel/locking/lockdep.c | 3 ++- kernel/stacktrace.c | 5 +++-- mm/debug.c | 40 ++++++++++++++++++------------------- mm/filemap.c | 2 +- mm/gup_test.c | 4 ++-- mm/huge_memory.c | 4 ++-- mm/kasan/report.c | 4 ++-- mm/kfence/report.c | 3 ++- mm/kmemleak.c | 2 +- mm/memory.c | 2 +- mm/memory_hotplug.c | 4 ++-- mm/page_alloc.c | 4 ++-- mm/page_isolation.c | 2 +- mm/page_owner.c | 24 +++++++++++----------- 25 files changed, 88 insertions(+), 69 deletions(-)