From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
mhocko@suse.cz, hare@suse.de,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()
Date: Fri, 23 Aug 2013 12:58:22 -0700 [thread overview]
Message-ID: <20130823125822.b3f5b946ef1e86c52834d0c3@linux-foundation.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1308232146250.25124@deuxcents.site>
On Fri, 23 Aug 2013 21:48:36 +0200 (CEST) Jiri Kosina <jkosina@suse.cz> wrote:
> > > We have customers (quite a few of them actually) which have machines with
> > > lots of SCSI disks attached (due to multipath etc.) and during boot when
> > > these disks are discovered and partitions set up quite some printing
> > > happens - multiplied by the number of devices (1000+) it is too much for a
> > > serial console to handle quickly enough. So these machines aren't able to
> > > boot with serial console enabled.
> >
> > It sounds like rather a corner case, not worth mucking up the critical
> > core logging code.
>
> Andrew, I have to admit I don't understand this argument at all.
Of course you do. print should be simple, robust and have minimum
dependency on other kernel parts.
I suppose that if you make the proposed
/proc/sys/kernel/max_printk_chars settable from the boot command line
and default to zero, any risks are minimized.
Baling out if oops_in_progress was a good thing also.
next prev parent reply other threads:[~2013-08-23 19:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 8:08 Jan Kara
2013-08-21 8:08 ` [PATCH 1/4] printk: Remove separate printk_sched buffers and use printk buf instead Jan Kara
2013-08-21 8:08 ` [PATCH 2/4] irq_work: Provide a irq work that can be processed on any cpu Jan Kara
2013-08-21 18:49 ` Steven Rostedt
2013-09-05 15:56 ` Jan Kara
2013-08-21 8:08 ` [PATCH 3/4] printk: Defer printing to irq work when we printed too much Jan Kara
2013-08-21 19:06 ` Steven Rostedt
2013-08-21 8:08 ` [PATCH 4/4] printk: Use unbound irq work for printing and waking Jan Kara
2013-08-21 19:24 ` Steven Rostedt
2013-08-21 21:27 ` [PATCH 0/4 v6] Avoid softlockups in console_unlock() Andrew Morton
2013-08-21 22:59 ` Jan Kara
2013-08-22 19:49 ` Andrew Morton
2013-08-22 21:57 ` Jan Kara
2013-08-22 22:14 ` Andrew Morton
2013-08-23 19:50 ` Jiri Kosina
2013-08-23 19:48 ` Jiri Kosina
2013-08-23 19:58 ` Andrew Morton [this message]
2013-08-26 11:48 ` Jiri Kosina
2013-09-05 15:46 ` Jan Kara
2013-09-19 21:26 ` Andrew Morton
2013-09-20 21:55 ` Jan Kara
2013-11-07 21:48 Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130823125822.b3f5b946ef1e86c52834d0c3@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hare@suse.de \
--cc=jack@suse.cz \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®