| 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
| ||
|
Message-ID: <20110112111401.4879d928@bob.linux.org.uk> Date: Wed, 12 Jan 2011 11:14:01 +0000 From: Alan Cox <alan@...ux.intel.com> To: Feng Tang <feng.tang@...el.com> Cc: linux-kernel@...r.kernel.org, gregkh@...e.de, akpm@...ux-foundation.org Subject: Re: [PATCH] console: prevent registered consoles from dumping old kernel message over again On Wed, 12 Jan 2011 14:48:46 +0800 Feng Tang <feng.tang@...el.com> wrote: > For a platform with many consoles like: > "console=tty1 console=ttyMFD2 console=ttyS0 earlyprintk=mrst" > > Each time when the non "selected_console" (tty1 and ttyMFD2 here) get > registered, the existing kernel message will be printed out on > registered consoles again, the "mrst" early console will get some > same message for 3 times, and "tty1" will get some for twice. > > So try to temporarily disable registered console's printing when dump > the existing kernel messages to the new console. I don't think the existing behaviour should be changed because other systems and users rely on it. Perhaps we need to be able to do console=xxx addconsole=yyy or some such instead so the user can indicate if the console should get all the messages so far or just be added as an extra console -- 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