Messages in this thread | | | Date | Mon, 25 Jun 2018 10:41:22 +0900 | From | Sergey Senozhatsky <> | Subject | Re: [PATCH] printk: inject caller information into the body of message |
| |
On (06/22/18 22:06), Tetsuo Handa wrote: > > > > Awesome. If you and Fengguang can combine forces and lead the > > whole thing towards "we couldn't care of pr_cont() less", it > > would be really huuuuuge. Go for it! > > Can't we have seq_printf()-like one which flushes automatically upon seeing '\n' > or buffer full? Printing memory information is using a lot of pr_cont(), even in > function names (e.g. http://lkml.kernel.org/r/20180622083949.GR10465@dhcp22.suse.cz ). > Since OOM killer code is serialized by oom_lock, we can use static buffer for > OOM killer messages.
I'm not the right guy to answer this question. Sorry. We need to Cc MM people on this.
Does OOM's pr_cont() usage cause too much disturbance to syzkaller? I thought that OOM was slightly out of sight.
-ss
| |