netdev - tg3 link autoneg on one port results in packets loss on other port

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>] [day] [month] [year] [list]

Message-ID: <CABVbdp__Rj=Si8EFazOD-gctgcs30gWB3Q8J9wqSLcKfio5HyQ@mail.gmail.com>
Date:	Fri, 25 Mar 2016 12:41:01 +0100
From:	vincent Richard <vincent.richard449@...il.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: tg3 link autoneg on one port results in packets loss on other port

Hi all,
I am using a HP DL360p server with broadcom BCM5719 ethernet card
handled by tg3 driver.
When the link is renegotiated on one ethernet port, out packets get
lost on other ethernet ports. The problem is easily reproducible by
looping on switch port up/down.
Instrumenting the driver, I observed that tg3_setup_phy() may last
more than 40 msec while holding the spin lock.
Is it possible to modify the tg3 driver so as to minimize link
renegotiation  impact ?
Thanks in advance for your help.