netdev - Re: macb: inconsistent Rx descriptor chain after OOM

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: <51458d2e-69a5-2a30-2167-7f47a43d9a2f@microchip.com>
Date:   Mon, 16 Sep 2019 10:00:27 +0000
From:   <Claudiu.Beznea@...rochip.com>
To:     <schwab@...e.de>, <Nicolas.Ferre@...rochip.com>
CC:     <netdev@...r.kernel.org>
Subject: Re: macb: inconsistent Rx descriptor chain after OOM

Hi Andreas,

I will have a look on it. It would be good if you could give me some
details about the steps to reproduce it.

Thank you,
Claudiu Beznea

On 16.09.2019 10:41, Andreas Schwab wrote:
> When there is an OOM situation, the macb driver cannot recover from it:
> 
> [245622.872993] macb 10090000.ethernet eth0: Unable to allocate sk_buff
> [245622.891438] macb 10090000.ethernet eth0: inconsistent Rx descriptor chain
> 
> After that, the interface is dead.  Since this system is using NFS root,
> it then stalled as a whole.
> 
> Andreas.
>