[lkml]   [2016]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] printk: avoid livelock if another CPU printks continuously
On Tue, 09 Feb 2016 17:41:25 +0100
Denys Vlasenko <> wrote:

> > No, I mentioned the taking of console sem. The spamming task will be
> > trying that a bit, failing and then letting this CPU continue doing its
> > bidding.
> That's exactly what we *don't* want to happen.
> We want that other CPU to get the lock.

I know. I meant that if the task fails to get the lock, it will let the
other continue to do its bidding. Hence the multiple tries. But this is
moot, because it's just adding onto the hacks.

> How do you plan to achieve that, if not by giving it a grace period
> when it can grab a lock?

What really needs to be done is to find out why a CPU is spamming with
printks and fix that. Is it a bug that is triggering?

-- Steve

 \ /
  Last update: 2016-02-09 18:01    [W:0.070 / U:3.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site