From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: kernel: BUG: soft lockup - CPU#1 stuck for 22s! [kni_single:1782] Date: Mon, 16 Feb 2015 17:00:24 -0800 Message-ID: <20150217010024.GB30617@mhcomputing.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dev To: Jay Rolette Return-path: Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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.