From: "Pali Rohár" <pali.rohar@gmail.com>
To: Mattias Jacobsson <2pi@mok.nu>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
michal.lkml@markovi.net, Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] platform/x86: wmi: add WMI support to MODULE_DEVICE_TABLE()
Date: Mon, 28 Jan 2019 15:27:01 +0100 [thread overview]
Message-ID: <20190128142701.xj4vwiind4ddbcj6@pali> (raw)
In-Reply-To: <20190128140911.xsltdctpk3bya7ya@mok.nu>
On Monday 28 January 2019 15:09:11 Mattias Jacobsson wrote:
> Hi,
>
> On 2019-01-27, Andy Shevchenko wrote:
> > On Sun, Jan 27, 2019 at 9:04 PM Mattias Jacobsson <2pi@mok.nu> wrote:
> > >
> > > The kernel provides the macro MODULE_DEVICE_TABLE() where driver authors
> > > can specify their device type and their array of device_ids and thereby
> > > trigger the generation of the appropriate MODULE_ALIAS() output. This is
> > > opposed to having to specify one MODULE_ALIAS() for each device. The WMI
> > > device type is currently not supported.
> > >
> > > While using MODULE_DEVICE_TABLE() does increase the complexity as well
> > > as spreading out the implementation across the kernel, it does come with
> > > some benefits too;
> > > * It makes different drivers look more similar; if you can specify the
> > > array of device_ids any device type specific input to MODULE_ALIAS()
> > > will automatically be generated for you.
> > > * It helps each driver avoid keeping multiple versions of the same
> > > information in sync. That is, both the array of device_ids and the
> > > potential multitude of MODULE_ALIAS()'s.
> > >
> > > Add WMI support to MODULE_DEVICE_TABLE() by adding info about struct
> > > wmi_device_id in devicetable-offsets.c and add a WMI entry point in
> > > file2alias.c.
> > >
> > > The type argument for MODULE_DEVICE_TABLE(type, name) is wmi.
> >
> > > +/* Looks like: wmi:guid */
> > > +static int do_wmi_entry(const char *filename, void *symval, char *alias)
> > > +{
> > > + DEF_FIELD_ADDR(symval, wmi_device_id, guid_string);
> > > + if (strlen(*guid_string) != WMI_GUID_STRING_LEN) {
> > > + warn("Invalid WMI device id 'wmi:%s' in '%s'\n",
> > > + *guid_string, filename);
> > > + return 0;
> > > + }
> >
> > > + if (snprintf(alias, 500, WMI_MODULE_PREFIX "%s", *guid_string) < 0) {
> >
> > What the point to use snprintf here with arbitrary buffer size if we
> > exactly know 2 facts:
> > 1. UUID string is 36 characters
> > 2. buffer is long enough
> >
> > ?
>
> As long as no one changes the code, not much.
At least instead of hardcoded number 500, you should use pass size of alias:
static int do_wmi_entry(const char *filename, void *symval, char *alias, size_t alias_size)
if (snprintf(alias, alias_size, WMI_MODULE_PREFIX "%s", *guid_string) < 0) {
Or pass buffer of constant size and then you do not need to use snprintf:
#define ALIAS_SIZE (sizeof(WMI_MODULE_PREFIX)+WMI_GUID_STRING_LEN)
static int do_wmi_entry(const char *filename, void *symval, char alias[ALIAS_SIZE])
This should not break even when code around changes.
> >
> > > + warn("Could not generate all MODULE_ALIAS's in '%s'\n",
> > > + filename);
> > > + return 0;
> > > + }
> > > + return 1;
> > > +}
> >
> > --
> > With Best Regards,
> > Andy Shevchenko
>
> Thanks,
> Mattias
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2019-01-28 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 19:03 [PATCH v2 0/3] " Mattias Jacobsson
2019-01-27 19:03 ` [PATCH v2 1/3] platform/x86: wmi: move struct wmi_device_id to mod_devicetable.h Mattias Jacobsson
2019-01-27 20:20 ` Andy Shevchenko
2019-01-28 13:54 ` Mattias Jacobsson
2019-01-28 16:01 ` Andy Shevchenko
2019-01-27 19:03 ` [PATCH v2 2/3] platform/x86: wmi: add WMI support to MODULE_DEVICE_TABLE() Mattias Jacobsson
2019-01-27 20:22 ` Andy Shevchenko
2019-01-28 14:09 ` Mattias Jacobsson
2019-01-28 14:27 ` Pali Rohár [this message]
2019-01-28 15:09 ` Mattias Jacobsson
2019-01-27 19:03 ` [PATCH v2 3/3] platform/x86: wmi: use MODULE_DEVICE_TABLE() instead of MODULE_ALIAS() Mattias Jacobsson
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=20190128142701.xj4vwiind4ddbcj6@pali \
--to=pali.rohar@gmail.com \
--cc=2pi@mok.nu \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yamada.masahiro@socionext.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®