[net,0/2] __napi_schedule_irqoff() used in wrong context

Message ID	20191126222013.1904785-1-bigeasy@linutronix.de
Headers	show Return-Path: <netdev-owner@vger.kernel.org> From: Sebastian Andrzej Siewior <bigeasy@linutronix.de> To: netdev@vger.kernel.org Cc: "David S. Miller" <davem@davemloft.net>, Thomas Gleixner <tglx@linutronix.de> Subject: [PATCH net 0/2] __napi_schedule_irqoff() used in wrong context Date: Tue, 26 Nov 2019 23:20:11 +0100 Message-Id: <20191126222013.1904785-1-bigeasy@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: netdev-owner@vger.kernel.org Precedence: bulk
Series	__napi_schedule_irqoff() used in wrong context \| expand [net,0/2] __napi_schedule_irqoff() used in wrong context [net,1/2] amd-xgbe: Use __napi_schedule() in BH context [net,2/2] net: gro: Let the timeout timer expire in softirq context with `threadirqs'

Message ID

20191126222013.1904785-1-bigeasy@linutronix.de

Headers

From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH net 0/2] __napi_schedule_irqoff() used in wrong context
Date: Tue, 26 Nov 2019 23:20:11 +0100
Message-Id: <20191126222013.1904785-1-bigeasy@linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: netdev-owner@vger.kernel.org
Precedence: bulk

Series

__napi_schedule_irqoff() used in wrong context | expand

Message

Sebastian Andrzej Siewior Nov. 26, 2019, 10:20 p.m. UTC

I found three cases where __napi_schedule_irqoff() could be used with
enabled interrupts while looking for something else… There are patches
for two of them.

The third one, hyperv/netvsc, is wrong with the `threadirqs' commandline
option because the interrupt will be delivered directly via the vector
and not the thread. I will try to sort this out with the x86 folks.

Sebastian