From: Hans de Goede <hdegoede@redhat.com>
To: Tong Zhang <ztong0001@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-acpi <linux-acpi@vger.kernel.org>
Subject: acpi_get_devices() crash when acpi_disabled==true (was [PATCH v2] drm/privacy-screen: honor acpi=off in detect_thinkpad_privacy_screen)
Date: Wed, 26 Jan 2022 14:47:24 +0100 [thread overview]
Message-ID: <6a0233cd-d931-8a36-3b9e-08b774cec7b0@redhat.com> (raw)
In-Reply-To: <20220123091004.763775-1-ztong0001@gmail.com>
Hi All,
On 1/23/22 10:10, Tong Zhang wrote:
> when acpi=off is provided in bootarg, kernel crash with
>
> [ 1.252739] BUG: kernel NULL pointer dereference, address: 0000000000000018
> [ 1.258308] Call Trace:
> [ 1.258490] ? acpi_walk_namespace+0x147/0x147
> [ 1.258770] acpi_get_devices+0xe4/0x137
> [ 1.258921] ? drm_core_init+0xc0/0xc0 [drm]
> [ 1.259108] detect_thinkpad_privacy_screen+0x5e/0xa8 [drm]
> [ 1.259337] drm_privacy_screen_lookup_init+0xe/0xe85 [drm]
>
> The reason is that acpi_walk_namespace expects acpi related stuff
> initialized but in fact it wouldn't when acpi is set to off. In this case
> we should honor acpi=off in detect_thinkpad_privacy_screen().
>
> Signed-off-by: Tong Zhang <ztong0001@gmail.com>
Thank you for catching this and thank you for your patch. I was about to merge
this, but then I realized that this might not be the best way to fix this.
A quick grep shows 10 acpi_get_devices() calls outside of drivers/acpi,
and at a first glance about half of those are missing an acpi_disabled
check. IMHO it would be better to simply add an acpi_disabled check to
acpi_get_devices() itself.
Rafael, do you agree ?
Note the just added chrome privacy-screen check uses
acpi_dev_present(), this is also used in about 10 places outside
of drivers/acpi and AFAIK none of those do an acpi_disabled check.
acpi_dev_present() uses bus_find_device(&acpi_bus_type, ...)
but the acpi_bus_type does not get registered when acpi_disabled
is set. In the end this is fine though since bus_find_device
checks for the bus not being registered and then just returns
NULL.
Regards,
Hans
> ---
> v2: fix typo in previous commit -- my keyboard is eating letters
>
> drivers/gpu/drm/drm_privacy_screen_x86.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_privacy_screen_x86.c b/drivers/gpu/drm/drm_privacy_screen_x86.c
> index a2cafb294ca6..e7aa74ad0b24 100644
> --- a/drivers/gpu/drm/drm_privacy_screen_x86.c
> +++ b/drivers/gpu/drm/drm_privacy_screen_x86.c
> @@ -33,6 +33,9 @@ static bool __init detect_thinkpad_privacy_screen(void)
> unsigned long long output;
> acpi_status status;
>
> + if (acpi_disabled)
> + return false;
> +
> /* Get embedded-controller handle */
> status = acpi_get_devices("PNP0C09", acpi_set_handle, NULL, &ec_handle);
> if (ACPI_FAILURE(status) || !ec_handle)
next prev parent reply other threads:[~2022-01-26 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 9:10 [PATCH v2] drm/privacy-screen: honor acpi=off in detect_thinkpad_privacy_screen Tong Zhang
2022-01-26 13:47 ` Hans de Goede [this message]
2022-01-26 14:25 ` acpi_get_devices() crash when acpi_disabled==true (was [PATCH v2] drm/privacy-screen: honor acpi=off in detect_thinkpad_privacy_screen) Hans de Goede
2022-01-26 15:54 ` Rafael J. Wysocki
2022-01-26 16:41 ` Hans de Goede
2022-01-26 17:11 ` Rafael J. Wysocki
2022-01-27 13:05 ` Hans de Goede
2022-01-27 13:33 ` Rafael J. Wysocki
2022-01-27 13:39 ` Hans de Goede
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=6a0233cd-d931-8a36-3b9e-08b774cec7b0@redhat.com \
--to=hdegoede@redhat.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tzimmermann@suse.de \
--cc=ztong0001@gmail.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
all inboxes | Powered by JetHome®