lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 26 Oct 2017 10:37:37 -0400
From:   Johannes Weiner <>
To:     Tetsuo Handa <>
Cc:,,, Cong Wang <>,
        Dave Hansen <>,
        Mel Gorman <>, Michal Hocko <>,
        Petr Mladek <>,
        Sergey Senozhatsky <>,
        Vlastimil Babka <>,
        "yuwang.yuwang" <>
Subject: Re: [PATCH] mm: don't warn about allocations which stall for too long

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 <>
> Reported-by: Cong Wang <>
> Reported-by: yuwang.yuwang <>
> Reported-by: Johannes Weiner <>
> Cc: Michal Hocko <>
> Cc: Vlastimil Babka <>
> Cc: Mel Gorman <>
> Cc: Dave Hansen <>
> Cc: Sergey Senozhatsky <>
> Cc: Petr Mladek <>

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 <>

Thanks Tetsuo!

Powered by blists - more mailing lists