linux-kernel - Re: [Libusb-devel] Kernel bug message and missing data on libusb_interrupt

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]

Message-ID: <Pine.LNX.4.44L0.1104051040440.1972-100000@iolanthe.rowland.org>
Date:	Tue, 5 Apr 2011 10:42:24 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Oncaphillis <oncaphillis@...fu.de>
cc:	Xiaofan Chen <xiaofanc@...il.com>,
	<libusb-devel@...ts.sourceforge.net>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [Libusb-devel] Kernel bug message and missing data on
 libusb_interrupt_transfer

On Tue, 5 Apr 2011, Oncaphillis wrote:

> On 04/05/2011 04:13 PM, Alan Stern wrote:
> > On Tue, 5 Apr 2011, Oncaphillis wrote:
> >
> >> Now I get
> >>
> >> <snip>
> >> ------------[ cut here ]------------
> >> kernel BUG at mm/slub.c:2808!
> >> invalid opcode: 0000 [#2] SMP
> > Can you duplicate this using either a 2.6.37 or 2.6.38 kernel?
> >
> > Alan Stern
> >
> The highest kernel version we've tried (as far as i remember) was the
> 2.6.36. Have there been issues which might have been solved betwen 36 
> and 3(7|8) ?

I don't know.  But the core kernel developers always want to hear about
problems reported against the most recent version possible.  If you
could test 2.6.39-rc1 (or -rc2, which should be released in a day or
so), that would be even better.

> I'll give it a try.

Thanks.

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/