On Thu 23-04-20 23:14:37, Tetsuo Handa wrote: > On 2020/04/23 23:06, Michal Hocko wrote: > >> Last year I proposed > >> https://lkml.kernel.org/r/1550896930-12324-1-git-send-email-penguin-kernel@xxxxxxxxxxxxxxxxxxx > >> and Sergey Senozhatsky commented > >> > >> "This is a bit of a strange issue, to be honest. If OOM prints too > >> many messages then we might want to do some work on the OOM side." > >> > >> . I was thinking that printing to consoles is a requirement for oom_dump_tasks . > >> > >> If we can agree with not printing dump_tasks() output to consoles, a trivial > >> patch shown below will solve the problem. Those who cannot run syslog daemon > >> in userspace might disagree, but this will be the simplest answer. > > > > Talk to printk people about this. > > > > Already CC'ed. In a separate thread please. > My question for you is are you OK with "not printing dump_tasks() output > to consoles?" . To be honest, I do not know whether that make sense. This sounds like something that people might have different opinions on and therefore it should be configured from the userspace. It is a policy which output goes where. All we should be dealing with is a log level. But as I've said this is something for printk maintainers. I have said I am ok with tweaking log levels in the oom report. -- Michal Hocko SUSE Labs
