From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752111Ab3JaE0G (ORCPT ); Thu, 31 Oct 2013 00:26:06 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:36684 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750807Ab3JaE0E (ORCPT ); Thu, 31 Oct 2013 00:26:04 -0400 Date: Thu, 31 Oct 2013 00:26:02 -0400 (EDT) Message-Id: <20131031.002602.2030884257299947291.davem@davemloft.net> To: xiyou.wangcong@gmail.com Cc: tdmackey@booleanhaiku.com, mchan@broadcom.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] bnx2: Use dev_kfree_skb_any() in bnx2_tx_int() From: David Miller In-Reply-To: References: <20131030.173200.2256841895208134119.davem@davemloft.net> X-Mailer: Mew version 6.5 on Emacs 24.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.1 (shards.monkeyblade.net [0.0.0.0]); Wed, 30 Oct 2013 21:26:03 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Cong Wang Date: Wed, 30 Oct 2013 15:01:12 -0700 > On Wed, Oct 30, 2013 at 2:32 PM, David Miller wrote: >> >> Explain to me then why other ethernet drivers implemented identically, >> such as tg3, can use plain dev_kfree_skb() just fine? > > I don't think they are fine, I just don't see bug reports > for them. At very least, I saw a same bug report for be2net too. > > To reproduce this bug, we need to find some one calling printk() > within IRQ handler, which seems rare? It seems there are few > people using hpsa driver together with netconsole. We've had this conversation before I believe, and I absolutely do not want to have to add IRQ safety to every ->poll() implementation. We have to provide a softint compatible environment for this callback to run in else everything is completely broken. All these drivers can safely assume softirq safe locking is sufficient, you're suggesting we need to take this hardirq safety and I'm really not willing to allow things to go that far. A lot of effort has been expended precisely to avoid that kind of overhead and cost.