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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1104081034510.1992-100000@iolanthe.rowland.org>
Date:	Fri, 8 Apr 2011 10:37:48 -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 Fri, 8 Apr 2011, Oncaphillis wrote:

> Just a short update,
> 
>   It doesn't seem to have anything to do with the libsub-1.0.x) version but
> with the --(enable|disable)-timerfd option of libusb configure. If 
> libusb was
> configured with --disable-timerfd, which was the case for our 1.0.6 libusb
> I get the kernel bug message in in slub.c module and eventually a
> kernel freeze. This holds true for libusb-1.0.8 and kernel 2.6.38.2

Can you post an example of the bug message (together with an
explanation of what you did to cause it) to LKML?  Change the Subject:  
line to something highly visible, like "Kernel BUG in 2.6.38.2 slub.c".

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/