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: <8e92cb31-f35a-6f4b-7409-035e87c0818a@de.ibm.com> Date: Tue, 12 Dec 2017 09:56:05 +0100 From: Christian Borntraeger <borntraeger@...ibm.com> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Cc: Jiri Slaby <jslaby@...e.com>, linux-serial@...r.kernel.org, linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] serial: forbid 8250 on s390 On 12/12/2017 09:48 AM, Greg Kroah-Hartman wrote: > On Tue, Dec 12, 2017 at 09:08:35AM +0100, Christian Borntraeger wrote: >> Using "make kvmconfig" results in a potentially unusable linux image >> on s390. The reason is that both the (default on s390) sclp consoles >> as well as the 8250 console register a ttyS<x> as console. Since there >> will be no 8250 on s390 let's fence 8250. This will ensure that there >> is always a working sclp console. >> >> Reported-by: Alice Frosi <alice@...ux.vnet.ibm.com> >> Signed-off-by: Christian Borntraeger <borntraeger@...ibm.com> >> Reviewed-by: Hendrik Brueckner <brueckner@...ux.vnet.ibm.com> >> --- >> drivers/tty/serial/8250/Kconfig | 1 + >> 1 file changed, 1 insertion(+) > > Does this need to be backported to any stable kernels? Or does anyone > who runs them on s390 already have this config option disabled? All shipped s390 kernels have 8250 disabled anyway. A backport of this patch could be helpful to let users who want to use "make kvmconfig" give a working configuration but it is certainly not critical. Christian
Powered by blists - more mailing lists