Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

Tejun Heo
2018-01-17T15:15:16Z

Hello,

On Wed, Jan 17, 2018 at 10:12:08AM +0100, Petr Mladek wrote:
> IMHO, the bad scenario with OOM was that any printk() called in
> the OOM report became console_lock owner and was responsible
> for pushing all new messages to the console. There was a possible
> livelock because OOM Killer was blocked in console_unlock() while
> other CPUs repeatedly complained about failed allocations.

I don't know why we're constantly back into this same loop on this
topic but that's not the problem we've been seeing. There are no
other CPUs involved.

It's great that Steven's patches solve a good number of problems. It
is also true that there's a class of problems that it doesn't solve,
which other approaches do. The productive thing to do here is trying
to solve the unsolved one too, especially given that it doesn't seem
too difficuilt to do so on top of what's proposed.

Thanks.

--
tejun