netdev - Re: r8169 regression: UDP packets dropped intermittantly

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: <20160601003123.GE3384@marvin.atrad.com.au>
Date:	Wed, 1 Jun 2016 10:01:23 +0930
From:	Jonathan Woithe <jwoithe@...ad.com.au>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	netdev@...r.kernel.org
Subject: Re: r8169 regression: UDP packets dropped intermittantly

On Wed, May 18, 2016 at 04:21:37PM +0930, Jonathan Woithe wrote:
> On Thu, Apr 07, 2016 at 12:14:18PM +0930, Jonathan Woithe wrote:
> > On Mon, Feb 08, 2016 at 01:03:19PM +1030, Jonathan Woithe wrote:
> > > On Wed, Dec 02, 2015 at 12:58:52AM +0100, Francois Romieu wrote:
> > > > Jonathan Woithe <jwoithe@...ad.com.au> :
> > > > [...]
> > > > > Any thoughts or progress at this stage?  Are there further tests you need me
> > > > > to do ?
> > > > 
> > > > Yes but you should expect two more days without signal.
> > > 
> > > FYI I am now back from annual leave and linux.conf.au.  This means I am in
> > > a position to test possible solutions to this problem once you are able to
> > > make them available.
> > 
> > Has there been any further progress on this problem?  I still have access to
> > the hardware and systems if further tests are required.
> 
> To assist in picking up this issue I thought I'd summarise where things are
> at from my perspective.
> 
> The problem is that small low-speed UDP packets are being dropped by the
> r8169-based network card in our systems.  Git bisect showed that the
> regression started with commit da78dbff2e05630921c551dbbc70a4b7981a8fff.
> :

FYI I have just tested the kernel.org 4.6 kernel and unsurprisingly it still
exhibits the regression.

Is there anything more I can do to move this forward?  I really do not want
to limit our systems to old kernels[1] just to avoid this regression, but
that is what I have to do while the regression remains.

Regards
  jonathan

[1] We are currently on 2.6.35.11 with some additional device driver patches
    we need for our hardware (which have subsequently been merged into
    mainline).  The regression is present in all kernels starting with 3.3
    which means the latest kernel we can use at present is 3.2.x.