linux-kernel - Re: BUG: unable to handle kernel paging request in usb_match

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:	Sun, 5 Aug 2012 09:58:26 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Oliver Neukum <oneukum@...e.de>,
	Bjørn Mork <bjorn@...k.no>,
	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	linux-kernel@...r.kernel.org,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>
Subject: Re: BUG: unable to handle kernel paging request in usb_match_id()

On Sun, Aug 05, 2012 at 10:59:38AM +0800, Fengguang Wu wrote:
> Hi all,
> 
> This line triggers an oops in kvm boot test:
> 
> usb_match_id():
> ==>      748         for (; id->idVendor || id->idProduct || id->bDeviceClass ||
>          749                id->bInterfaceClass || id->driver_info; id++) {
>          750                 if (usb_match_one_id(interface, id))
>          751                         return id;
>          752         }
> 
> It's an old bug and happens also in linux 3.0. It's very reproducible
> for the attached config. I can send the initrd (yocto-minimal-i386.cgz)
> on your request in private email.

Odds are a driver without a terminating NULL for the device id list is
causing this to fail.

What devices are in the system and what drivers are trying to be bound?

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/