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
| ||
|
Date: Fri, 10 Nov 2006 15:23:20 +1100 From: Keith Owens <kaos@....com> To: Bjorn Helgaas <bjorn.helgaas@...com> cc: linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org Subject: Re: KDB blindly reads keyboard port Bjorn Helgaas (on Tue, 26 Sep 2006 13:54:30 -0600) wrote: >get_kbd_char() in arch/ia64/kdb/kdba_io.c does "inb(KBD_STATUS_REG)". > >But we don't know whether there's even an i8042 keyboard controller >present. On HP ia64 boxes, there is no i8042, and trying to read >from it can cause an MCA. > >This depends on the specific platform and how it is configured. I >observed this MCA while booting the SLES10 install kernel on an >HP rx7620 in "default" acpiconfig mode. The supported acpiconfig >mode on this box is "single-pci-domain", which also puts some >legacy ports into "soft-fail" mode, where the read will just return >0xff instead of causing an MCA. But I think it's wrong to blindly >poke around in I/O port space. Bjron, could you try kdb-v4.4-2.6.19-rc5-{common,ia64}-2 on your problem system? I changed kdb so it only uses the keyboard if at least one console matches the pattern /^tty[0-9]*$/. IOW, if the user specifies an i8042 style console on the command line (or uses the default with CONFIG_VT=y) then kdb will attempt to use that keyboard. Otherwise kdb ignores a VT style console, even when the kernel is compiled with CONFIG_VT=y. - 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/
Powered by blists - more mailing lists