lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 1 Nov 2021 21:00:23 +0200 From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com> To: Aditya Garg <gargaditya08@...e.com> Cc: Lee Jones <lee.jones@...aro.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Orlando Chamberlain <redecorating@...tonmail.com> Subject: Re: [PATCH v1 1/1] mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe() On Mon, Nov 01, 2021 at 06:21:51PM +0000, Aditya Garg wrote: > > On 01-Nov-2021, at 8:40 PM, Andy Shevchenko <andriy.shevchenko@...ux.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. > Following patch fixed the issue for me. > Tested-by: Aditya Garg <gargaditya08@...e.com> Thanks for testing! -- With Best Regards, Andy Shevchenko
Powered by blists - more mailing lists