linux-kernel - Re: [PATCH] console: prevent registered consoles from dumping old kernel message over again

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110112145009.352c3517@lxorguk.ukuu.org.uk>
Date:	Wed, 12 Jan 2011 14:50:09 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Feng Tang <feng.tang@...el.com>
Cc:	Alan Cox <alan@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"gregkh@...e.de" <gregkh@...e.de>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: Re: [PATCH] console: prevent registered consoles from dumping old
 kernel message over again

> Don't know if I understand correctly, but with this patch all the consoles
> still will get the full version of kernel messages, it just save some
> console from dumping some of the early messages several times.
> 
> Still use the old example, assume log0 is the kernel messages from boot start to
> the point where tty1 get registered, log1 is from tty1's registering to
> ttyMFD2's, log2 is the rest kernel message. Before this patch, on the
> boot console, we will see: log0 + log0 + log1 + log0 + log1 + log2.

Sorry misunderstood the point of the patch - yes that makes sense !
--
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/