From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934420AbdDFRdQ (ORCPT ); Thu, 6 Apr 2017 13:33:16 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:34334 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933269AbdDFRdI (ORCPT ); Thu, 6 Apr 2017 13:33:08 -0400 Date: Thu, 6 Apr 2017 19:33:06 +0200 From: Pavel Machek To: Jan Kara Cc: "Eric W. Biederman" , Sergey Senozhatsky , Ye Xiaolong , Sergey Senozhatsky , Steven Rostedt , Petr Mladek , Andrew Morton , Linus Torvalds , Peter Zijlstra , "Rafael J . Wysocki" , Greg Kroah-Hartman , Jiri Slaby , Len Brown , linux-kernel@vger.kernel.org, lkp@01.org Subject: Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage Message-ID: <20170406173306.GD10363@amd> References: <20170329092511.3958-9-sergey.senozhatsky@gmail.com> <20170330213829.GA21476@inn.lkp.intel.com> <20170331023506.GB3493@jagdpanzerIV.localdomain> <20170331040438.GA366@jagdpanzerIV.localdomain> <20170331063913.GE20961@yexl-desktop> <20170331144730.GA10578@tigerII.localdomain> <87a881v52o.fsf@xmission.com> <20170403093152.GB15168@quack2.suse.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C1iGAkRnbeBonpVg" Content-Disposition: inline In-Reply-To: <20170403093152.GB15168@quack2.suse.cz> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --C1iGAkRnbeBonpVg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > This patch set gives up part of the printk() reliability for bounded > latency (at least unless we detect we are really in trouble) which is IMHO > a good trade-off for lots of users (and others can just turn this feature > off). If they can ever realize they were bitten by this feature. Can we go for different tradeoff? In console_unlock(), if you detect too much work, print "Too many messages to print, %d bytes delayed" and wake up kernel thread. You still get the latency, and people bitten by this feature will at least get fair warning. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --C1iGAkRnbeBonpVg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAljme9IACgkQMOfwapXb+vICiwCfTje9AV4xYPosQ7waQfBSD9ZM vhkAnjbQjOgAKlUPnx1OGvO6b5GRe9DD =keA0 -----END PGP SIGNATURE----- --C1iGAkRnbeBonpVg--