From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: v5.13-rcX regression - NULL pointer dereference - MFD and software node API
Date: Tue, 22 Jun 2021 11:09:55 +0300 [thread overview]
Message-ID: <YNGa021IIj+C8H7h@kuha.fi.intel.com> (raw)
In-Reply-To: <YNCw5k9vwdQiS0u4@owl.dominikbrodowski.net>
On Mon, Jun 21, 2021 at 05:31:50PM +0200, Dominik Brodowski wrote:
> Am Mon, Jun 21, 2021 at 01:37:59PM +0300 schrieb Heikki Krogerus:
> > On Mon, Jun 21, 2021 at 01:00:06PM +0300, Andy Shevchenko wrote:
> > > Can you, please, attach this to the bug report?
> > >
> > > Long story here is that the device creation fails but we already have added
> > > swnode to it. Meanwhile, device itself is not completely instantiated (yet)
> > > and dev_name(dev) is NULL. The software_node_notify() is called with such
> > > device and Oopses in the following line
> > >
> > > sysfs_remove_link(&swnode->kobj, dev_name(dev));
> > >
> > > My patch fixes another issue that might happen before this and in the code
> > > that retrieves swnode itself in the device_remove_software_node().
> > >
> > > Of course my patch won't fix this issue.
> > >
> > > I have heard that Heikki is looking how to fix the issue in your case and
> > > potentially in any other cases where device_add_software_node() is called
> > > against not formed object instance.
> >
> > Dominik, can you test the attached patch to confirm if this really is
> > the case.
>
> With this patch applied, the panic disappears.
Thanks Dominik. I'll clean it and send it out today.
cheers,
--
heikki
next prev parent reply other threads:[~2021-06-22 8:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 8:26 v5.13-rcX regression - NULL pointer dereference - MFD and software node API Dominik Brodowski
2021-06-20 11:19 ` Andy Shevchenko
2021-06-20 11:49 ` Dominik Brodowski
2021-06-20 16:36 ` Andy Shevchenko
2021-06-20 18:27 ` Andy Shevchenko
2021-06-21 8:59 ` Dominik Brodowski
2021-06-21 10:00 ` Andy Shevchenko
2021-06-21 10:37 ` Heikki Krogerus
2021-06-21 15:31 ` Dominik Brodowski
2021-06-22 8:09 ` Heikki Krogerus [this message]
2021-06-22 14:10 ` Heikki Krogerus
2021-06-22 14:36 ` Dominik Brodowski
2021-06-22 15:28 ` Andy Shevchenko
2021-06-22 17:19 ` Dominik Brodowski
2021-06-22 15:28 ` Andy Shevchenko
2021-06-22 15:30 ` Andy Shevchenko
2021-06-23 10:51 ` Heikki Krogerus
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=YNGa021IIj+C8H7h@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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