netdev - Re: defxx: skb_push() failing?

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, 28 Mar 2013 00:11:20 -0400
From:	David Oostdyk <daveo@...mit.edu>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
CC:	Eric Dumazet <eric.dumazet@...il.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: defxx: skb_push() failing?

Hi Maciej,

I can confirm that the two FDDI cards work on a 32-bit kernel. I'm not 
getting anywhere near the data rates I'd expect (3.5MB/sec?) but it's a 
start.  I'd be glad to help test any 64-bit patches you come up with, 
Maciej.

Either way, Eric Dumazet's patch to drivers/block/aoe/aoecmd.c seems to 
be required to prevent a panic right after defxx is loaded.  Eric - good 
find.  Should your patch be submitted upstream, then?

Dave O.

On 03/26/13 15:00, Maciej W. Rozycki wrote:
> On Tue, 26 Mar 2013, David Oostdyk wrote:
>
>> (Now if I could only figure out why these FDDI cards don't want to talk to
>> each other... I was hoping that was it.)
>   I saw 64-bit addresses in your log -- the driver is known not to be
> 64-bit-clean, I've had an initial look into it recently and will be
> addressing it shortly.
>
>    Maciej
> --
> 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

Download attachment "smime.p7s" of type "application/pkcs7-signature" (4567 bytes)