Re: [RFC PATCH 2/5] mm: lower the printk loglevel for __dump_page messages

2018-12-12 Thread Michal Hocko
On Wed 12-12-18 15:25:40, Michal Hocko wrote: > It seems one follow up fix got lost on my side. Andrew, could you fold > this in please? > > diff --git a/mm/debug.c b/mm/debug.c > index 68e9a9f2df16..4c916e1abedc 100644 > --- a/mm/debug.c > +++ b/mm/debug.c > @@ -88,7 +88,7 @@ void __dump_page(str

Re: [RFC PATCH 2/5] mm: lower the printk loglevel for __dump_page messages

2018-12-12 Thread Michal Hocko
It seems one follow up fix got lost on my side. Andrew, could you fold this in please? diff --git a/mm/debug.c b/mm/debug.c index 68e9a9f2df16..4c916e1abedc 100644 --- a/mm/debug.c +++ b/mm/debug.c @@ -88,7 +88,7 @@ void __dump_page(struct page *page, const char *reason) pr_warn("flags: %#

Re: [RFC PATCH 2/5] mm: lower the printk loglevel for __dump_page messages

2018-11-15 Thread Baoquan He
On 11/07/18 at 11:18am, Michal Hocko wrote: > From: Michal Hocko > > __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 c

[RFC PATCH 2/5] mm: lower the printk loglevel for __dump_page messages

2018-11-07 Thread Michal Hocko
From: Michal Hocko __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