From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186])
 by dpdk.org (Postfix) with ESMTP id 7888DB643
 for <dev@dpdk.org>; Tue, 17 Feb 2015 02:00:54 +0100 (CET)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id 5DD8F80C005; Mon, 16 Feb 2015 17:00:24 -0800 (PST)
Date: Mon, 16 Feb 2015 17:00:24 -0800
From: Matthew Hall <mhall@mhcomputing.net>
To: Jay Rolette <rolette@infiniteio.com>
Message-ID: <20150217010024.GB30617@mhcomputing.net>
References: <CADNuJVpqB+kydPe1QXcLV21GRF-TMR9dkXdYysk7XTdBZryhcQ@mail.gmail.com>
 <CADNuJVpKGyFOKNA1JCVbg72SwPbM0+9HSWAHwAiG=G2AXFKJ-w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADNuJVpKGyFOKNA1JCVbg72SwPbM0+9HSWAHwAiG=G2AXFKJ-w@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: Dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] kernel: BUG: soft lockup - CPU#1 stuck for 22s!
 [kni_single:1782]
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2015 01:00:54 -0000

On Mon, Feb 16, 2015 at 10:33:52AM -0600, Jay Rolette wrote:
> In kni_net_rx_normal(), it was calling netif_receive_skb() instead of
> netif_rx(). The source for netif_receive_skb() point out that it should
> only be called from soft-irq context, which isn't the case for KNI.

For the uninitiated among us, what was the practical effect of the coding 
error? Waiting forever for a lock which will never be available in IRQ 
context, or causing unintended re-entrancy, or what?

Thanks,
Matthew.