linux-kernel - Re: [PATCH 01/30] disallow SERIAL_8250_PNP with SERIAL_8250

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]

Date:	Tue, 24 Mar 2009 22:18:16 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Andrey Panin <pazke@...pac.ru>, linux-kernel@...r.kernel.org,
	linux-serial@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH 01/30] disallow SERIAL_8250_PNP with SERIAL_8250_CONSOLE

On Tue, 24 Mar 2009 21:43:21 +0000
Matthew Garrett <mjg59@...f.ucam.org> wrote:

> On Tue, Mar 24, 2009 at 09:38:41PM +0000, Alan Cox wrote:
> > > > Since the conversion to drivers/serial - so years.
> > > 
> > > So everyone using serial console with 8250_PNP enabled gets a crash on 
> > > boot, and has done for years? Really?
> > 
> > If their console port is PnP listed yes.
> 
> So this patch breaks the case where a kernel with PNP support is booted 
> on a system without PNP-listed serial ports? Do we know the ratio of 
> machines fixed by this compared to the machines broken?

Well the original patch came from Red Hat so perhaps they can provide
data based on their userbase ?
--
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/