| 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: <Pine.LNX.4.44L0.0810171046530.2178-100000@iolanthe.rowland.org> Date: Fri, 17 Oct 2008 10:58:28 -0400 (EDT) From: Alan Stern <stern@...land.harvard.edu> To: Jeremy Fitzhardinge <jeremy@...p.org> cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-usb <linux-usb@...r.kernel.org> Subject: Re: Oops in UHCI when encountering "host controller process error" On Thu, 16 Oct 2008, Jeremy Fitzhardinge wrote: > Looks like this is the relevent detail: "uhci->skelqh[1]->node.next is > NULL" for all the queues. Haven't looked into it yet. > ------------[ cut here ]------------ > WARNING: at /home/jeremy/hg/xen/paravirt/linux/drivers/usb/host/uhci-q.c:1744 uhci_scan_schedule+0xb7/0x9a3() > uhci->skelqh[1]->node.next is NULL Odd. Is skelqh[1] the only entry whose node.next is NULL? Not skelqh[2] or others? The node is initialized during uhci_start() in uhci-hcd.c -- there's a loop which initializes all the uhci->skelqh[i] entries by calling uhci_alloc_qh(). You should check inside that loop to see whether uhci->skelqh[i]->node.next is NULL to begin with. If it is then something about the DMA-coherent memory is funny; if not then the linked list pointer gets corrupted somewhere. Alan Stern -- 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