From: Lee Jones <lee.jones@linaro.org>
To: Aditya Garg <gargaditya08@live.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Orlando Chamberlain <redecorating@protonmail.com>
Subject: Re: [PATCH v2 1/1] mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
Date: Tue, 16 Nov 2021 15:53:21 +0000 [thread overview]
Message-ID: <YZPT8YfVXlNlBpY9@google.com> (raw)
In-Reply-To: <PN2PR01MB44118FFB624CD71D6C3F0FF5B8989@PN2PR01MB4411.INDPRD01.PROD.OUTLOOK.COM>
On Mon, 15 Nov 2021, Aditya Garg wrote:
>
> ________________________________
> From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Sent: Monday, November 15, 2021 4:06 PM
> To: Aditya Garg
> Cc: Lee Jones; linux-kernel@vger.kernel.org; Orlando Chamberlain
> Subject: Re: [PATCH v2 1/1] mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
>
> On Tue, Nov 02, 2021 at 05:42:35AM +0000, Aditya Garg wrote:
> > > On 02-Nov-2021, at 12:30 AM, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>
> > > The runtime PM callback may be called as soon as the runtime PM facility
> > > is enabled and activated. It means that ->suspend() may be called before
> > > we finish probing the device in the ACPI case. Hence, NULL pointer
> > > dereference:
> > >
> > > intel-lpss INT34BA:00: IRQ index 0 not found
> > > BUG: kernel NULL pointer dereference, address: 0000000000000030
> > > ...
> > > Workqueue: pm pm_runtime_work
> > > RIP: 0010:intel_lpss_suspend+0xb/0x40 [intel_lpss]
> > >
> > > To fix this, first try to register the device and only after that enable
> > > runtime PM facility.
> > >
> > > Fixes: 4b45efe85263 ("mfd: Add support for Intel Sunrisepoint LPSS devices")
> > > Reported-by: Orlando Chamberlain <redecorating@protonmail.com>
> > > Reported-by: Aditya Garg <gargaditya08@live.com>
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > Tested-by: Aditya Garg <gargaditya08@live.com>
> > > ---
> > > v2: added tag (Aditya), returned 0 explicitly at the end of ->probe()
>
> > It works
>
> Thanks for testing again!
>
> Lee, can we have this as a fix material for v5.16-rcX?
Generally not, no.
We usually only push patches for the -rcs if they fix something that
was broken during the merge window. Not 6+ years ago. :)
However, if other valid fixes appear, I'll shove it into the PR too.
> I would like to have it backported to stable 5.15 too.
Yes, once it's merged into mainline, it will be back-ported as far
back as it applies cleanly.
If you have a specific kernel in mind, you should indicate it on the
end of the Fixes line.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-11-16 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 19:00 [PATCH v2 1/1] mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe() Andy Shevchenko
2021-11-02 5:42 ` Aditya Garg
2021-11-15 10:36 ` Andy Shevchenko
[not found] ` <PN2PR01MB44118FFB624CD71D6C3F0FF5B8989@PN2PR01MB4411.INDPRD01.PROD.OUTLOOK.COM>
2021-11-16 15:53 ` Lee Jones [this message]
[not found] ` <258423E3-A0D4-4E24-BCD1-42F7ED25BB88@live.com>
2021-11-18 8:40 ` Lee Jones
2021-11-29 11:59 ` Lee Jones
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=YZPT8YfVXlNlBpY9@google.com \
--to=lee.jones@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gargaditya08@live.com \
--cc=linux-kernel@vger.kernel.org \
--cc=redecorating@protonmail.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