linux-kernel - Re: libusb broken on 2.6.28 x86

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:	Fri, 02 Jan 2009 03:25:13 -0500
From:	Mark Lord <lkml@....ca>
To:	Greg KH <gregkh@...e.de>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org
Subject: Re: libusb broken on 2.6.28 x86_64 ?

Mark Lord wrote:
> Greg KH wrote:
>> On Fri, Jan 02, 2009 at 02:51:13AM -0500, Mark Lord wrote:
>>> Greg KH wrote:
>>>> On Fri, Jan 02, 2009 at 02:01:21AM -0500, Mark Lord wrote:
>>>>> Mark Lord wrote:
>>> ..
>>>>> Mmm.. broken only for 64-bit userspace, it seems.
>>>>>
>>>>> I've recompiled the same app against 32-bit libs,
>>>>> and it works just fine on that 64-bit system,
>>>>> as well as on 32-bit systems.
>>>>>
>>>>> But not when compiled for pure 64-bit operation on a 64-bit system.
>>> ..
>>>> Which version of libusb, a new one was just released a few weeks ago
>>>> that fixes a lot of problems reported in the older libusb versions, and
>>>> made things much faster to boot.  You might want to check it out.
>>> ..
>>>
>>> This is with libusb-0.1-4, which has been working fine with all prior 
>>> kernels,
>>> including the 2.6.27.xx series.
>>>
>>> Userspace stuff like this is not supposed to be broken from kernel to 
>>> kernel.
>>
>> No it shouldn't, I was thinking this was the first time you had tried
>> such a thing (64bit userspace apps.)
>>
>> If using 2.6.27 works, then we need to fix this.
> ..
> 
> Yup.  I don't really see anything likely in kernel from 2.6.27 to 2.6.28,
> other than perhaps the new "poisoning" code.  I wonder if that could be it?
> 
> Kinda weird that the device works with libusb the first time it is used,
> but then fails on all subsequent runs of the same app, until replugged.
> 
> But.. I can run the 32-bit compat app after a 64-bit failure,
> and *that* does work.  There's gotta be a useful clue in there somewhere.
..

It is failing on the very first submiturb call, getting -ENOENT back:

open("/dev/bus/usb/004/002", O_RDWR)    = 3
ioctl(3, USBDEVFS_GETDRIVER, 0x7fff5d0486b0) = -1 ENODATA (No data available)
ioctl(3, USBDEVFS_CLAIMINTERFACE, 0x7fff5d0487bc) = 0
ioctl(3, USBDEVFS_CLEAR_HALT, 0x7fff5d0487c4) = 0
ioctl(3, USBDEVFS_SUBMITURB, 0x7fff5d0486c0) = -1 ENOENT (No such file or directory)

--
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/