From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Kurt Borja <kuurtb@gmail.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Hans de Goede <hdegoede@redhat.com>,
Mark Pearson <mpearson-lenovo@squebb.ca>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-riscv@lists.infradead.org,
Damian Tometzki <damian@riscv-rocks.de>
Subject: Re: [PATCH] platform/x86: thinkpad_acpi: Fix NULL pointer dereferences while probing
Date: Tue, 1 Apr 2025 14:24:36 +0300 (EEST) [thread overview]
Message-ID: <455d5e7d-6f1e-a0a0-773b-85c26418bf54@linux.intel.com> (raw)
In-Reply-To: <20250330-thinkpad-fix-v1-1-4906b3fe6b74@gmail.com>
On Sun, 30 Mar 2025, Kurt Borja wrote:
> Some subdrivers make use of the global reference tpacpi_pdev during
> initialization, which is called from the platform driver's probe.
> However, after
>
> commit 38b9ab80db31 ("platform/x86: thinkpad_acpi: Move subdriver initialization to tpacpi_pdriver's probe.")
>
Next time, please include these into the paragraph flow normally obeying
the normal paragraph formatting. I changed them in this case.
> this variable is only properly initialized *after* probing and this can
> result in a NULL pointer dereference.
>
> In order to fix this without reverting the commit, register the platform
> bundle in two steps, first create and initialize tpacpi_pdev, then
> register the driver synchronously with platform_driver_probe(). This way
> the benefits of commit 38b9ab80db31 are preserved.
>
> Additionally,
>
> commit 43fc63a1e8f6 ("platform/x86: thinkpad_acpi: Move HWMON initialization to tpacpi_hwmon_pdriver's probe")
>
> introduced a similar problem, however tpacpi_sensors_pdev is only used
> once inside the probe, so replace the global reference with the one
> given by the probe.
>
> Reported-by: Damian Tometzki <damian@riscv-rocks.de>
> Closes: https://lore.kernel.org/r/CAL=B37kdL1orSQZD2A3skDOevRXBzF__cJJgY_GFh9LZO3FMsw@mail.gmail.com/
> Fixes: 38b9ab80db31 ("platform/x86: thinkpad_acpi: Move subdriver initialization to tpacpi_pdriver's probe.")
> Fixes: 43fc63a1e8f6 ("platform/x86: thinkpad_acpi: Move HWMON initialization to tpacpi_hwmon_pdriver's probe")
> Tested-by: Damian Tometzki <damian@riscv-rocks.de>
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
Applied to the review-ilpo-fixes branch.
> ---
> Hi all,
>
> The commit message is pretty self-explanatory. I have one question
> though. As you can see in the crash dump of the original report:
>
> Mar 29 17:43:16.180758 fedora kernel: ? asm_exc_page_fault+0x26/0x30
> Mar 29 17:43:16.180769 fedora kernel: ? __pfx_klist_children_get+0x10/0x10
> Mar 29 17:43:16.180781 fedora kernel: ? kobject_get+0xd/0x70
> Mar 29 17:43:16.180792 fedora kernel: device_add+0x8f/0x6e0
> Mar 29 17:43:16.180804 fedora kernel: rfkill_register+0xbc/0x2c0 [rfkill]
> Mar 29 17:43:16.180813 fedora kernel: tpacpi_new_rfkill+0x185/0x230 [thinkpad_acpi]
>
> The NULL dereference happens in device_add(), inside rfkill_register().
> This bothers me because, as you can see here:
>
> 1198 atp_rfk->rfkill = rfkill_alloc(name,
> 1199 &tpacpi_pdev->dev,
> 1200 rfktype,
> 1201 &tpacpi_rfk_rfkill_ops,
> 1202 atp_rfk);
>
> the NULL deference happens in line 1199, inside tpacpi_new_rfkill(). I
> think this disagreement might be due to compile time optimizations?
How did you map it to line numbers? Is it just about difference in the
compiled binaries that results in different line numbers?
--
i.
> Well, if someone knows better, let me know!
>
> (This driver is going to give me nightmares, sorry for the bug!)
> ---
> drivers/platform/x86/thinkpad_acpi.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c
> index 0384cf31187872df90f5ac3def9b1d6617e82ed5..a17efb68664c9c7723daa2aba023ba0cbc6b96dd 100644
> --- a/drivers/platform/x86/thinkpad_acpi.c
> +++ b/drivers/platform/x86/thinkpad_acpi.c
> @@ -367,6 +367,7 @@ static struct {
> u32 beep_needs_two_args:1;
> u32 mixer_no_level_control:1;
> u32 battery_force_primary:1;
> + u32 platform_drv_registered:1;
> u32 hotkey_poll_active:1;
> u32 has_adaptive_kbd:1;
> u32 kbd_lang:1;
> @@ -11820,10 +11821,10 @@ static void thinkpad_acpi_module_exit(void)
> platform_device_unregister(tpacpi_sensors_pdev);
> }
>
> - if (tpacpi_pdev) {
> + if (tp_features.platform_drv_registered)
> platform_driver_unregister(&tpacpi_pdriver);
> + if (tpacpi_pdev)
> platform_device_unregister(tpacpi_pdev);
> - }
>
> if (proc_dir)
> remove_proc_entry(TPACPI_PROC_DIR, acpi_root_dir);
> @@ -11893,9 +11894,8 @@ static int __init tpacpi_pdriver_probe(struct platform_device *pdev)
>
> static int __init tpacpi_hwmon_pdriver_probe(struct platform_device *pdev)
> {
> - tpacpi_hwmon = devm_hwmon_device_register_with_groups(
> - &tpacpi_sensors_pdev->dev, TPACPI_NAME, NULL, tpacpi_hwmon_groups);
> -
> + tpacpi_hwmon = devm_hwmon_device_register_with_groups(&pdev->dev, TPACPI_NAME,
> + NULL, tpacpi_hwmon_groups);
> if (IS_ERR(tpacpi_hwmon))
> pr_err("unable to register hwmon device\n");
>
> @@ -11965,16 +11965,24 @@ static int __init thinkpad_acpi_module_init(void)
> tp_features.quirks = dmi_id->driver_data;
>
> /* Device initialization */
> - tpacpi_pdev = platform_create_bundle(&tpacpi_pdriver, tpacpi_pdriver_probe,
> - NULL, 0, NULL, 0);
> + tpacpi_pdev = platform_device_register_simple(TPACPI_DRVR_NAME, PLATFORM_DEVID_NONE,
> + NULL, 0);
> if (IS_ERR(tpacpi_pdev)) {
> ret = PTR_ERR(tpacpi_pdev);
> tpacpi_pdev = NULL;
> - pr_err("unable to register platform device/driver bundle\n");
> + pr_err("unable to register platform device\n");
> thinkpad_acpi_module_exit();
> return ret;
> }
>
> + ret = platform_driver_probe(&tpacpi_pdriver, tpacpi_pdriver_probe);
> + if (ret) {
> + pr_err("unable to register main platform driver\n");
> + thinkpad_acpi_module_exit();
> + return ret;
> + }
> + tp_features.platform_drv_registered = 1;
> +
> tpacpi_sensors_pdev = platform_create_bundle(&tpacpi_hwmon_pdriver,
> tpacpi_hwmon_pdriver_probe,
> NULL, 0, NULL, 0);
>
> ---
> base-commit: 1a9239bb4253f9076b5b4b2a1a4e8d7defd77a95
> change-id: 20250330-thinkpad-fix-98db0d8c3be3
>
> Best regards,
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-04-01 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 15:39 [PATCH] platform/x86: thinkpad_acpi: Fix NULL pointer dereferences while probing Kurt Borja
2025-03-30 18:43 ` Kurt Borja
2025-03-31 17:26 ` Genes Lists
2025-04-01 11:24 ` Ilpo Järvinen [this message]
2025-04-01 14:43 ` Kurt Borja
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=455d5e7d-6f1e-a0a0-773b-85c26418bf54@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=damian@riscv-rocks.de \
--cc=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
/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