From: "Barnabás Pőcze" <pobrn@protonmail.com>
To: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Mark Gross <markgross@kernel.org>,
Hans de Goede <hdegoede@redhat.com>, Armin Wolf <W_Armin@gmx.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [RFC PATCH v1] platform/x86: wmi: Do not register driver with invalid GUID
Date: Sat, 15 Jul 2023 21:24:16 +0000 [thread overview]
Message-ID: <20230715211604.1272227-1-pobrn@protonmail.com> (raw)
Since a WMI driver's ID table contains strings it is relatively
easy to make mistakes. At the moment, there is no feedback
if any of the specified GUIDs are invalid (since
028e6e204ace1f080cfeacd72c50397eb8ae8883).
So check if the GUIDs in the driver's ID table are valid,
print all invalid ones, and refuse to register the driver
if any of the GUIDs are invalid.
Signed-off-by: Barnabás Pőcze <pobrn@protonmail.com>
---
drivers/platform/x86/wmi.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/drivers/platform/x86/wmi.c b/drivers/platform/x86/wmi.c
index a78ddd83cda0..bf0be40b418a 100644
--- a/drivers/platform/x86/wmi.c
+++ b/drivers/platform/x86/wmi.c
@@ -1513,6 +1513,19 @@ static int acpi_wmi_probe(struct platform_device *device)
int __must_check __wmi_driver_register(struct wmi_driver *driver,
struct module *owner)
{
+ bool any_id_invalid = false;
+
+ for (const struct wmi_device_id *id = driver->id_table; *id->guid_string; id++) {
+ if (!uuid_is_valid(id->guid_string)) {
+ pr_err("driver '%s' has invalid GUID: %s",
+ driver->driver.name, id->guid_string);
+ any_id_invalid = true;
+ }
+ }
+
+ if (any_id_invalid)
+ return -EINVAL;
+
driver->driver.owner = owner;
driver->driver.bus = &wmi_bus_type;
--
2.41.0
next reply other threads:[~2023-07-15 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 21:24 Barnabás Pőcze [this message]
2023-07-17 9:49 ` [RFC PATCH v1] platform/x86: wmi: Do not register driver with invalid GUID Andy Shevchenko
2023-07-17 11:23 ` Barnabás Pőcze
2023-07-17 11:31 ` Andy Shevchenko
2023-07-19 19:23 ` Barnabás Pőcze
2023-07-20 8:36 ` Andy Shevchenko
2023-07-20 10:42 ` Barnabás Pőcze
2023-07-21 9:17 ` Andy Shevchenko
2023-07-26 8:45 ` Hans de Goede
2023-07-27 22:54 ` Barnabás Pőcze
2023-07-28 10:02 ` Andy Shevchenko
2023-07-28 14:39 ` Barnabás Pőcze
2023-07-31 19:52 ` Andy Shevchenko
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=20230715211604.1272227-1-pobrn@protonmail.com \
--to=pobrn@protonmail.com \
--cc=W_Armin@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--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