netdev - Re: r8169 driver from kernel 5.0 crashing

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, 4 Apr 2019 21:41:38 +0200
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     VDR User <user.vdr@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: r8169 driver from kernel 5.0 crashing - napi_consume_skb

On 04.04.2019 16:28, VDR User wrote:
> Hi,
> 
> Unfortunately I have to report that the crashing has resurfaced. I'm
> currently using kernel 5.0 with Heiner's fix applied. In the last few
> days I've had the crash occur 4 times now. I'm not sure how to further
> investigate this but I'm guessing a patch that adds more debugging
> output will be needed to track down where exactly things go bad and
> hopefully what exactly is triggering it? In 2 cases there was
> bi-directional traffic, in the other 2 cases there was only incoming
> traffic. In all cases the nic became unresponsive, all connections to
> the box died/timed out. After roughly 10 minutes the nic came back to
> life on its own without my intervention. The odd thing I noticed was
> the dmesg log showing the problem only shows up once in dmesg instead
> of 4 times to coincide with the 4 crashes/freezes. I don't think the
> box reboot itself, and if it did then dmesg should be clean.
> 
> Please let me know what you think and how we should proceed. Thanks!
> Derek
> 
Instead of having to wait for the issue: Can you trigger it with iperf3
in either direction?