linux-kernel - Re: [PATCH] printk: avoid livelock if another CPU printks continuously

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <20160209113326.501867bc@gandalf.local.home>
Date:	Tue, 9 Feb 2016 11:33:26 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Denys Vlasenko <dvlasenk@...hat.com>
Cc:	linux-kernel@...r.kernel.org, srostedt@...hat.com,
	Tejun Heo <tj@...nel.org>,
	Peter Hurley <peter@...leysoftware.com>
Subject: Re: [PATCH] printk: avoid livelock if another CPU printks
 continuously

On Tue, 09 Feb 2016 17:07:42 +0100
Denys Vlasenko <dvlasenk@...hat.com> wrote:

> On 02/09/2016 04:50 PM, Steven Rostedt wrote:
> > One thing is to find the spamming code and fix that.  
> 
> We can't rely that there won't be never-ending concurrent printks,
> right? For one, in many setups user can cause printk flood.

No, that would be a bug. This is why we have printk_ratelimit for.

> 
> I think we must ensure that printk does not livelock.

printk is a kernel utility. The users of printk must ensure this.

-- Steve