On Thu, Oct 26, 2017 at 08:28:59PM +0900, Tetsuo Handa wrote: > [...] it is possible to trigger OOM lockup and/or soft lockups when > many threads concurrently called warn_alloc() (in order to warn > about memory allocation stalls) due to current implementation of > printk(), and it is difficult to obtain useful information due to > limitation of synchronous warning approach. > > [...] > > Signed-off-by: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx> > Reported-by: Cong Wang <xiyou.wangcong@xxxxxxxxx> > Reported-by: yuwang.yuwang <yuwang.yuwang@xxxxxxxxxxxxxxx> > Reported-by: Johannes Weiner <hannes@xxxxxxxxxxx> > Cc: Michal Hocko <mhocko@xxxxxxxxxx> > Cc: Vlastimil Babka <vbabka@xxxxxxx> > Cc: Mel Gorman <mgorman@xxxxxxx> > Cc: Dave Hansen <dave.hansen@xxxxxxxxx> > Cc: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx> > Cc: Petr Mladek <pmladek@xxxxxxxx> It would have been nice to be able to fix it instead, because there is value in having the lockup detection. But it's true that it currently causes more problems than it solves. Back to the drawing board for now. Acked-by: Johannes Weiner <hannes@xxxxxxxxxxx> Thanks Tetsuo! -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
