netdev - Re: [PATCH net-next] bnx2x: avoid soft lockup in bnx2x

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:	Tue, 08 Dec 2015 22:55:27 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	netdev@...r.kernel.org, ariel.elior@...gic.com, willemb@...gle.com
Subject: Re: [PATCH net-next] bnx2x: avoid soft lockup in bnx2x_poll()

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Tue, 08 Dec 2015 05:54:40 -0800

> From: Eric Dumazet <edumazet@...gle.com>
> 
> Under heavy TX load, bnx2x_poll() can loop forever and trigger
> soft lockup bugs.
> 
> A napi poll handler must yield after one TX completion round,
> risk of livelock is too high otherwise.
> 
> Bug is very easy to trigger using a debug build, and udp flood, because
> of added cpu cycles in TX completion, and we do not receive enough
> packets to break the loop.
> 
> Reported-by: Willem de Bruijn <willemb@...gle.com>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>

Indeed, no driver should ever do more than one TX completion round
per NAPI poll call, _ever_.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html