[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191018131532.dsfhyiilsi7cy4cm@linutronix.de>
Date: Fri, 18 Oct 2019 15:15:32 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Daniel Wagner <dwagner@...e.de>
Cc: UNGLinuxDriver@...rochip.com, netdev@...r.kernel.org,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rt-users@...r.kernel.org,
Woojung Huh <woojung.huh@...rochip.com>,
Marc Zyngier <maz@...nel.org>, Andrew Lunn <andrew@...n.ch>,
Stefan Wahren <wahrenst@....net>,
Jisheng Zhang <Jisheng.Zhang@...aptics.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] net: usb: lan78xx: Use phy_mac_interrupt() for interrupt
handling
On 2019-10-18 10:28:17 [+0200], Daniel Wagner wrote:
> handle_simple_irq() expect interrupts to be disabled. The USB
> framework is using threaded interrupts, which implies that interrupts
> are re-enabled as soon as it has run.
Without threading interrupts, this is invoked in pure softirq context
since commit ed194d1367698 ("usb: core: remove local_irq_save() around
->complete() handler") where the local_irq_disable() has been removed.
This is probably not a problem because the lock is never observed with
in IRQ context.
Wouldn't handle_nested_irq() work here instead of the simple thingy?
Sebastian
Powered by blists - more mailing lists