From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>,
linux-can@vger.kernel.org,
"Wolfgang Grandegger" <wg@grandegger.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Vincent Mailhol" <mailhol.vincent@wanadoo.fr>,
"Oliver Hartkopp" <socketcan@hartkopp.net>,
"Timo Schlüßler" <schluessler@krause.de>,
"Tim Harvey" <tharvey@gateworks.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Null pointer dereference in mcp251x driver when resuming from sleep
Date: Mon, 3 May 2021 15:49:22 +0200 [thread overview]
Message-ID: <8dcdeab9-80f1-5961-6d55-82b4904cbf14@kontron.de> (raw)
In-Reply-To: <YI/+OP4z787Tmd05@smile.fi.intel.com>
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.
prev parent reply other threads:[~2021-05-03 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 13:11 Null pointer dereference in mcp251x driver when resuming from sleep Frieder Schrempf
2021-05-03 13:44 ` Andy Shevchenko
2021-05-03 13:48 ` Andy Shevchenko
2021-05-03 13:54 ` Andy Shevchenko
2021-05-04 13:54 ` Frieder Schrempf
2021-05-04 14:19 ` Andy Shevchenko
2021-05-03 13:49 ` Frieder Schrempf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8dcdeab9-80f1-5961-6d55-82b4904cbf14@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=schluessler@krause.de \
--cc=socketcan@hartkopp.net \
--cc=tharvey@gateworks.com \
--cc=wg@grandegger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).