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
| ||
|
Date: Fri, 23 Aug 2013 21:48:36 +0200 (CEST) From: Jiri Kosina <jkosina@...e.cz> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Jan Kara <jack@...e.cz>, LKML <linux-kernel@...r.kernel.org>, mhocko@...e.cz, hare@...e.de, Steven Rostedt <rostedt@...dmis.org> Subject: Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock() On Thu, 22 Aug 2013, Andrew Morton 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. Do you feel comfortable having the code in the kernel that can be spinning for tenths of seconds with interrupts disabled? As that's the exact description of the current printk(). I feel very uncomfortable having a core kernel logging facility having such property. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists