From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Barnabás Pőcze" <pobrn@protonmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Mark Gross <markgross@kernel.org>, Armin Wolf <W_Armin@gmx.de>
Subject: Re: [RFC PATCH v1] platform/x86: wmi: Do not register driver with invalid GUID
Date: Fri, 28 Jul 2023 13:02:35 +0300 [thread overview]
Message-ID: <ZMOSO5HgpurayDsN@smile.fi.intel.com> (raw)
In-Reply-To: <pjVZC4te3dWaMwoS7jB1-n4z390Ohz0mvuCCUZHwiXlZVMjzwySf_DMa49RDmbhzfvkzRY3FI8zQ0xltNimu-GpBAqJ2Kc3SENu_fwJDJ7E=@protonmail.com>
On Thu, Jul 27, 2023 at 10:54:26PM +0000, Barnabás Pőcze wrote:
> 2023. július 26., szerda 10:45 keltezéssel, Hans de Goede <hdegoede@redhat.com> írta:
> > On 7/15/23 23:24, Barnabás Pőcze wrote:
...
> > I think that having an additional check like the one which you
> > propose has some value too, even if it is just to cover drivers
> > which for some reason don't use `MODULE_DEVICE_TABLE()`, but IMHO
> > the most important check to have is a check in file2alias.c .
>
> Okay... any tips on how to avoid copying `uuid_is_valid()`?
I think I already told the rough design: we need to split uuid.c to three
files: libuuid.h, libuuid.c uuid.c and libuuid.c should be built twice:
once for uuid.c and once for file2alias.c. libuuid.h should contain the
definitions file2alias.c is using. Something like that.
> Another idea I had was that maybe `struct wmi_device_id::guid_string` needs to be
> changed to be `guid_t` and then `GUID_INIT()` or something similar could be used
> to initialize it. That way it is impossible to mess up the format. The only downside
> I can see is that guid is no longer "grep-able".
Strictly speaking you may not do that because it's a (semi-)ABI.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-07-28 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 21:24 [RFC PATCH v1] platform/x86: wmi: Do not register driver with invalid GUID Barnabás Pőcze
2023-07-17 9:49 ` 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 [this message]
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=ZMOSO5HgpurayDsN@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@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