From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932882AbdC2VnU (ORCPT ); Wed, 29 Mar 2017 17:43:20 -0400 Received: from mail-wr0-f169.google.com ([209.85.128.169]:34506 "EHLO mail-wr0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932706AbdC2Vln (ORCPT ); Wed, 29 Mar 2017 17:41:43 -0400 MIME-Version: 1.0 In-Reply-To: <20170329.143014.2001816338079751776.davem@davemloft.net> References: <1490784106-14489-1-git-send-email-vzakhar@synopsys.com> <20170329.143014.2001816338079751776.davem@davemloft.net> From: Eric Dumazet Date: Wed, 29 Mar 2017 14:41:40 -0700 Message-ID: Subject: Re: [PATCH] ezchip: nps_enet: check if napi has been completed To: David Miller Cc: Vladislav.Zakharov@synopsys.com, netdev , eladkan@mellanox.com, noamca@mellanox.com, LKML , linux-snps-arc@lists.infradead.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 29, 2017 at 2:30 PM, David Miller wrote: Signed-off-by: Vlad Zakharov > > Applied. > > Eric, if this is really required now, we have 148 broken drivers still. Piece of cake :/ If we get more reports like that, we might implement a logic to prevent infinite loops. It is not clear to me what exactly happened to this driver, since testing napi_complete_done() was not mandatory.