[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8dcdeab9-80f1-5961-6d55-82b4904cbf14@kontron.de>
Date: Mon, 3 May 2021 15:49:22 +0200
From: Frieder Schrempf <frieder.schrempf@...tron.de>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Marc Kleine-Budde <mkl@...gutronix.de>, linux-can@...r.kernel.org,
Wolfgang Grandegger <wg@...ndegger.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Vincent Mailhol <mailhol.vincent@...adoo.fr>,
Oliver Hartkopp <socketcan@...tkopp.net>,
Timo Schlüßler <schluessler@...use.de>,
Tim Harvey <tharvey@...eworks.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Null pointer dereference in mcp251x driver when resuming from
sleep
On 03.05.21 15:44, Andy Shevchenko wrote:
> On Mon, May 03, 2021 at 03:11:40PM +0200, Frieder Schrempf wrote:
>> Hi,
>>
>> with kernel 5.10.x and 5.12.x I'm getting a null pointer dereference
>> exception from the mcp251x driver when I resume from sleep (see trace
>> below).
>>
>> As far as I can tell this was working fine with 5.4. As I currently don't
>> have the time to do further debugging/bisecting, for now I want to at least
>> report this here.
>>
>> Maybe there is someone around who could already give a wild guess for what
>> might cause this just by looking at the trace/code!?
>
> Does revert of c7299fea6769 ("spi: Fix spi device unregister flow") help?
This commit is so new, that it is neither in 5.10.x nor in 5.12.1. So it
can't be the reason.
Powered by blists - more mailing lists