linux-kernel - Re: [RESEND][PATCH v2] register_console: prevent adding the same console twice

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] [day] [month] [year] [list]

Date:	Fri, 2 Aug 2013 18:37:44 +0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Andreas Bießmann <andreas@...ssmann.de>
Cc:	linux-kernel@...r.kernel.org, Kay Sievers <kay@...y.org>,
	Ben Hutchings <ben@...adent.org.uk>, stable@...r.kernel.org
Subject: Re: [RESEND][PATCH v2] register_console: prevent adding the same
 console twice

On Fri, Aug 02, 2013 at 12:23:34PM +0200, Andreas Bießmann wrote:
> This patch guards the console_drivers list to be corrupted. The
> for_each_console() macro insist on a strictly forward list ended by NULL:
> 
>  con0->next->con1->next->NULL
> 
> Without this patch it may happen easily to destroy this list for example by
> adding 'earlyprintk' twice, especially on embedded devices where the early
> console is often a single static instance.  This will result in the following
> list:
> 
>  con0->next->con0
> 
> This in turn will result in an endless loop in console_unlock() later on by
> printing the first __log_buf line endlessly.
> 
> Signed-off-by: Andreas Bießmann <andreas@...ssmann.de>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: Kay Sievers <kay@...y.org>
> Cc: Ben Hutchings <ben@...adent.org.uk>
> Cc: stable@...r.kernel.org

It's a nice "feature", but I fail to see how this is worthy of going
into the stable tree, as it's not fixing a kernel error, only a typo by
a user.

thanks,

greg k-h
--
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/