netdev - Re: BQL support in gianfar causes network hickup

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:	Wed, 6 Feb 2013 16:20:59 +0100
From:	"Keitel, Tino (ALC NetworX GmbH)" <Tino.Keitel@...networx.de>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
CC:	Eric Dumazet <eric.dumazet@...il.com>,
	Tino Keitel <tino.keitel@...ei.de>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: BQL support in gianfar causes network hickup

On Di, 2013-02-05 at 20:55 -0500, Paul Gortmaker wrote:
> How critical is ptp2 for this?  And/or the platform details?  I can
> try and reproduce it on an mpc8349 system and/or an mpc8548
> system (and even an mpc8641D system) but I'd rather know that
> was a meaningful chase and not a snipe hunt before going there.
> 
> So, in that respect, a "If you run this, you will get this" type of
> error message would be good.   I understand that may be too
> idealistic, though.

Hi,

I'm using an MPC8313ERDB board and was able to reproduce it with a
vanilla 3.6.7 kernel. There are some modifications to the device tree,
though. I'll try to reproduce this with as few changes to the device
tree as possible.

Ptp2 is critical for the desired use. So far I also only was able to
reproduce it with this ptp2 client.

If it is a possible option for you, I could provide an affected device
to make the issue easy to reproduce.

Regards,
Tino