netdev - Re: MV643xx Ethernet Driver Issue on a Motorola PrPMC-275 board.

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: <20080730235622.GA22826@xi.wantstofly.org>
Date:	Thu, 31 Jul 2008 01:56:22 +0200
From:	Lennert Buytenhek <buytenh@...tstofly.org>
To:	Chris Larson <clarson@...sta.com>
Cc:	netdev@...r.kernel.org
Subject: Re: MV643xx Ethernet Driver Issue on a Motorola PrPMC-275 board.

On Tue, Jul 29, 2008 at 10:49:09AM -0700, Chris Larson wrote:

> I was wondering if anyone had any advice on an issue a customer of ours 
> is running into.  When they run a series of bandwidth tests, slowly 
> increasing the bandwidth & # of tcp connections to roughly 30Mbit at 
> 4000 connections, their machine panics.  An address passed to 
> dma_unmap_single is beyond lowmem, as though it was corrupted in some 
> fashion.  The address is the data pointer in the ethernet dma 
> descriptors, it pulls a descriptor out of the ring in the packet receipt 
> functions and at that point the address is wrong.  Nowhere in the driver 
> is a descriptor set up with that address, yet the datasheet on the 
> mv643xx doesn't seem to indicate that the dma engine ever writes to the 
> descriptors themselves, only to the data they point to (as you'd 
> expect).  Does anyone have any ideas on this?  I'm afraid that I'm a bit 
> out of my depth on this issue.  The architecture is ppc.

I've never seen this happen.  Which kernel version is this on?
--
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