From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757406AbcBIQHp (ORCPT <rfc822;w@1wt.eu>);
	Tue, 9 Feb 2016 11:07:45 -0500
Received: from mx1.redhat.com ([209.132.183.28]:56615 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754648AbcBIQHo (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 9 Feb 2016 11:07:44 -0500
Message-ID: <56BA0ECE.2050106@redhat.com>
Date: Tue, 09 Feb 2016 17:07:42 +0100
From: Denys Vlasenko <dvlasenk@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Steven Rostedt <rostedt@goodmis.org>
CC: linux-kernel@vger.kernel.org, srostedt@redhat.com,
        Tejun Heo <tj@kernel.org>, Peter Hurley <peter@hurleysoftware.com>
Subject: Re: [PATCH] printk: avoid livelock if another CPU printks continuously
References: <1454963703-20433-1-git-send-email-dvlasenk@redhat.com>	<20160208161123.2ceb601d@gandalf.local.home>	<56B9FEE4.3010502@redhat.com>	<20160209101707.540641fb@gandalf.local.home>	<56BA04AD.7090903@redhat.com> <20160209105024.3606f233@gandalf.local.home>
In-Reply-To: <20160209105024.3606f233@gandalf.local.home>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.

I think we must ensure that printk does not livelock.