[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201026124753.btmdh3iwbwnff5dg@linutronix.de>
Date: Mon, 26 Oct 2020 13:47:53 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Johan Hovold <johan@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
"Ahmed S. Darwish" <a.darwish@...utronix.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-usb@...r.kernel.org,
Thomas Winischhofer <thomas@...ischhofer.net>,
Mathias Nyman <mathias.nyman@...el.com>,
Valentina Manea <valentina.manea.m@...il.com>,
Shuah Khan <shuah@...nel.org>,
Alan Stern <stern@...land.harvard.edu>,
linux-omap@...r.kernel.org, Kukjin Kim <kgene@...nel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, Felipe Balbi <balbi@...nel.org>,
Duncan Sands <duncan.sands@...e.fr>
Subject: Re: [patch V2 02/13] USB: serial: keyspan_pda: Replace
in_interrupt() usage
On 2020-10-25 17:56:47 [+0100], Johan Hovold wrote:
> There's a ton of issues with this driver, but this is arguably making
> things worse. A line discipline may call write() from just about any
> context so we cannot rely on tty being non-NULL here (e.g. PPP).
I wasn't aware of that. I've been looking at the callers each time a
`tty' was passed it looked like a preemptible context (due to mutex /
GFP_KERNEL) and so on.
>
> Johan
Sebastian
Powered by blists - more mailing lists