From: Baoquan He <bhe@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <OSalvador@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [RFC PATCH 2/5] mm: lower the printk loglevel for __dump_page messages
Date: Fri, 16 Nov 2018 08:56:34 +0800 [thread overview]
Message-ID: <20181116005634.GT2653@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20181107101830.17405-3-mhocko@kernel.org>
On 11/07/18 at 11:18am, Michal Hocko wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> __dump_page messages use KERN_EMERG resp. KERN_ALERT loglevel (this is
> the case since 2004). Most callers of this function are really detecting
> a critical page state and BUG right after. On the other hand the
> function is called also from contexts which just want to inform about
> the page state and those would rather not disrupt logs that much (e.g.
> some systems route these messages to the normal console).
>
> Reduce the loglevel to KERN_WARNING to make dump_page easier to reuse
> for other contexts while those messages will still make it to the kernel
> log in most setups. Even if the loglevel setup filters warnings away
> those paths that are really critical already print the more targeted
> error or panic and that should make it to the kernel log.
>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
> ---
> mm/debug.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/mm/debug.c b/mm/debug.c
> index a33177bfc856..d18c5cea3320 100644
> --- a/mm/debug.c
> +++ b/mm/debug.c
> @@ -54,7 +54,7 @@ void __dump_page(struct page *page, const char *reason)
> * dump_page() when detected.
> */
> if (page_poisoned) {
> - pr_emerg("page:%px is uninitialized and poisoned", page);
> + pr_warn("page:%px is uninitialized and poisoned", page);
> goto hex_only;
> }
>
> @@ -65,27 +65,27 @@ void __dump_page(struct page *page, const char *reason)
> */
> mapcount = PageSlab(page) ? 0 : page_mapcount(page);
>
> - pr_emerg("page:%px count:%d mapcount:%d mapping:%px index:%#lx",
> + pr_warn("page:%px count:%d mapcount:%d mapping:%px index:%#lx",
pr_warn("page:%px refcount:%d mapcount:%d mapping:%px index:%#lx",
Better print it as refcount since we have renamed it.
> page, page_ref_count(page), mapcount,
> page->mapping, page_to_pgoff(page));
> if (PageCompound(page))
> pr_cont(" compound_mapcount: %d", compound_mapcount(page));
> pr_cont("\n");
> if (PageAnon(page))
> - pr_emerg("anon ");
> + pr_warn("anon ");
> else if (PageKsm(page))
> - pr_emerg("ksm ");
> + pr_warn("ksm ");
> else if (mapping) {
> - pr_emerg("%ps ", mapping->a_ops);
> + pr_warn("%ps ", mapping->a_ops);
> if (mapping->host->i_dentry.first) {
> struct dentry *dentry;
> dentry = container_of(mapping->host->i_dentry.first, struct dentry, d_u.d_alias);
> - pr_emerg("name:\"%*s\" ", dentry->d_name.len, dentry->d_name.name);
> + pr_warn("name:\"%*s\" ", dentry->d_name.len, dentry->d_name.name);
> }
> }
> BUILD_BUG_ON(ARRAY_SIZE(pageflag_names) != __NR_PAGEFLAGS + 1);
>
> - pr_emerg("flags: %#lx(%pGp)\n", page->flags, &page->flags);
> + pr_warn("flags: %#lx(%pGp)\n", page->flags, &page->flags);
>
> hex_only:
> print_hex_dump(KERN_ALERT, "raw: ", DUMP_PREFIX_NONE, 32,
> @@ -93,11 +93,11 @@ void __dump_page(struct page *page, const char *reason)
> sizeof(struct page), false);
>
> if (reason)
> - pr_alert("page dumped because: %s\n", reason);
> + pr_warn("page dumped because: %s\n", reason);
>
> #ifdef CONFIG_MEMCG
> if (!page_poisoned && page->mem_cgroup)
> - pr_alert("page->mem_cgroup:%px\n", page->mem_cgroup);
> + pr_warn("page->mem_cgroup:%px\n", page->mem_cgroup);
> #endif
> }
>
> --
> 2.19.1
>
next prev parent reply other threads:[~2018-11-16 0:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 10:18 [RFC PATCH 0/5] mm, memory_hotplug: improve memory offlining failures debugging Michal Hocko
2018-11-07 10:18 ` [RFC PATCH 1/5] mm: print more information about mapping in __dump_page Michal Hocko
2018-11-24 0:04 ` Andrew Morton
2018-11-25 8:10 ` Michal Hocko
2018-11-07 10:18 ` [RFC PATCH 2/5] mm: lower the printk loglevel for __dump_page messages Michal Hocko
2018-11-16 0:56 ` Baoquan He [this message]
2018-12-12 14:25 ` Michal Hocko
2018-12-12 14:34 ` Michal Hocko
2018-11-07 10:18 ` [RFC PATCH 3/5] mm, memory_hotplug: drop pointless block alignment checks from __offline_pages Michal Hocko
2018-11-07 10:18 ` [RFC PATCH 4/5] mm, memory_hotplug: print reason for the offlining failure Michal Hocko
2018-11-07 22:04 ` Andrew Morton
2018-11-08 8:01 ` Michal Hocko
2018-11-13 8:02 ` Michal Hocko
2018-11-08 6:23 ` Anshuman Khandual
2018-11-08 7:59 ` Michal Hocko
2018-11-07 10:18 ` [RFC PATCH 5/5] mm, memory_hotplug: be more verbose for memory offline failures Michal Hocko
2018-11-08 7:16 ` Anshuman Khandual
2018-11-08 8:12 ` Michal Hocko
2018-11-08 8:19 ` Anshuman Khandual
2018-11-13 8:03 ` Michal Hocko
2018-11-16 0:07 ` Andrew Morton
2018-11-16 7:21 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181116005634.GT2653@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=OSalvador@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).