On Fri, 23 Aug 2013 21:48:36 +0200 (CEST) Jiri Kosina <jkos...@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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
