>-----Original Message----- >From: David Miller [mailto:davem@xxxxxxxxxxxxx] >Sent: Friday, March 14, 2014 11:59 AM >To: Kirsher, Jeffrey T >Cc: Tantilov, Emil S; netdev@xxxxxxxxxxxxxxx; >gospo@xxxxxxxxxx; sassmann@xxxxxxxxxx; asharma@xxxxxx; >stable@xxxxxxxxxxxxxxx; Keller, Jacob E >Subject: Re: [net-next 02/16] ixgbe: fix spinlock recursion >with netpoll and busy poll > >From: Jeff Kirsher <jeffrey.t.kirsher@xxxxxxxxx> >Date: Fri, 14 Mar 2014 02:47:12 -0700 > >> From: Emil Tantilov <emil.s.tantilov@xxxxxxxxx> >> >> This patch resolves a hang with busy poll when used with netconsole. >> >> The main change is the check for netpoll packets in ixgbe_poll() which >> prevents a call to spin_lock_bh() while interrupts are disabled. >> >> In addition it removes the call to netif_rx() since netif_receive_skb() >> can deal with netpoll packets and also replaced the global adapter flag >> with per-q_vector bool that indicates Rx packet from netpoll which >> should help with performance. >> >> CC: Arun Sharma <asharma@xxxxxx> >> CC: stable <stable@xxxxxxxxxxxxxxx> >> Signed-off-by: Jacob Keller <jacob.e.keller@xxxxxxxxx> >> Signed-off-by: Emil Tantilov <emil.s.tantilov@xxxxxxxxx> >> Tested-by: Phil Schmitt <phillip.j.schmitt@xxxxxxxxx> >> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@xxxxxxxxx> > >Eric Biederman and co. are working to make this completely unnecessary. > >What is going to happen is that poll will be called with a budget of >zero, and no RX processing will thus occur, for netpoll. > >Nothing in the RX path can handle being invoked from hardware >interrupt context, so we have to prevent it completely in all >drivers that support netpoll. I noticed Eric's patches and this is obviously the better way to deal with it, but once the netpoll_rx patches are accepted will they make it into previous stable releases? Currently kernels between 3.11 and 3.13 (assuming Eric's changes make it into 3.14) will hang when netpoll and busy poll are used together. Thanks, Emil -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html