netdev - Re: [PATCH] hso: fix for the 'invalid frame length' messages

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:	Thu, 02 Apr 2009 10:34:02 +0200
From:	Jan Dumon <j.dumon@...ion.com>
To:	David Miller <davem@...emloft.net>
CC:	linux-usb@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] hso: fix for the 'invalid frame length' messages

David Miller wrote:
> From: Jan Dumon <j.dumon@...ion.com>
> Date: Mon, 30 Mar 2009 11:44:59 +0200
> 
>> Some devices cannot send very short usb transfers. To get around this the
>> firmware adds a known pattern and flags the driver that it should check for
>> this pattern on short transfers. This flag was not taken into account by
>> the driver.
>>
>> Signed-off-by: Jan Dumon <j.dumon@...ion.com>
> 
> These patches do not apply cleanly, please respin them against the
> current sources.

The diff was taken against 2.6.29, problem is that they both change the same file (as did the
product ID patch) and that changes the line numbers...
Against which sources should I take them again and should I start from the same clean sources for
each patch or can they be "stacked" ?

Greets.
Jan.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html