linux-kernel - Re: [PATCH v2]vt: fix potential dual con

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:	Wed, 8 Jan 2014 20:33:49 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Wang YanQing <udknight@...il.com>, jslaby@...e.cz,
	airlied@...hat.com, akpm@...ux-foundation.org, kilobyte@...band.pl,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2]vt: fix potential dual con_driver register for
 conswitchp

On Mon, Dec 30, 2013 at 11:21:18AM +0800, Wang YanQing wrote:
> We should check whether conswitchp is registered before
> add it to registered_con_driver in con_init, or it will
> cause dual con_driver register for conswitchp.
> 
> Although I haven't met it in reality, but I think it could
> happen for Embeded devices, who register platform con_driver
> earlier than call con_init.

Does that happen on those systems?  Let's not add code that's never
going to be use, and is not needed, right?

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/