From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: dmaengine <dmaengine@vger.kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Sinan Kaya <okaya@codeaurora.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Vinod Koul <vinod.koul@intel.com>
Subject: Re: [PATCH v3 2/5] ACPI / bus: Do not traverse through non-existed device table
Date: Thu, 08 Feb 2018 18:13:03 +0200 [thread overview]
Message-ID: <1518106383.22495.206.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0iEB74dPUN400pfB4+AV--NZj7hs6aZGiSoSiz5cTS37g@mail.gmail.com>
On Thu, 2018-02-08 at 16:59 +0100, Rafael J. Wysocki wrote:
> On Wed, Feb 7, 2018 at 3:56 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > When __acpi_match_device() is called it would be possible to have
> > ACPI ID table a MULL pointer. To avoid potential dereference,
> > check for this before traverse.
> >
> > While here, remove redundant 'else'.
> >
> >
> > + if (ids) {
> > + for (id = ids; id->id[0] || id->cls; id++) {
> > + if (id->id[0] && !strcmp((char *)id-
> > >id, hwid->id))
> > + return id;
> > + if (id->cls &&
> > __acpi_match_device_cls(id, hwid))
> > + return id;
> > + }
> >
>
> The return value below should be updated in *this* patch, because this
> is what allows ids to be NULL in the first place.
OK, so I'll fold it into patch 1 then.
> And as far as I'm concerned you can do:
>
> if (!strcmp(ACPI_DT_NAMESPACE_HID, hwid->id)
> return (const struct acpi_device_id
> *)acpi_of_match_device(device, of_ids);
>
> and update the comment accordingly.
But it's still a trick.
Okay, what comes to my mind (yes, not so simple, but cleaner I suppose)
is to define
struct acpi_of_device_id {
struct acpi_device_id *acpi_id;
struct of_device_id *of_id;
};
Add a new parameter to acpi_of_match_device(..., struct
acpi_of_device_id *id).
Update __acpi_match_device() in the similar way.
Update callers.
It looks to me much more cleaner.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-02-08 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 14:56 [PATCH v3 1/5] ACPI / bus: Return error code from __acpi_match_device() in one case Andy Shevchenko
2018-02-07 14:56 ` [PATCH v3 2/5] ACPI / bus: Do not traverse through non-existed device table Andy Shevchenko
2018-02-08 15:59 ` Rafael J. Wysocki
2018-02-08 16:01 ` Rafael J. Wysocki
2018-02-08 16:13 ` Andy Shevchenko [this message]
2018-02-08 16:53 ` Andy Shevchenko
2018-02-08 17:06 ` Rafael J. Wysocki
2018-02-07 14:56 ` [PATCH v3 3/5] ACPI / bus: Remove checks in acpi_get_match_data() Andy Shevchenko
2018-02-07 14:56 ` [PATCH v3 4/5] ACPI / bus: Rename acpi_get_match_data() to acpi_device_get_match_data() Andy Shevchenko
2018-02-07 14:56 ` [PATCH v3 5/5] device property: Constify device_get_match_data() Andy Shevchenko
2018-02-08 15:14 ` [PATCH v3 1/5] ACPI / bus: Return error code from __acpi_match_device() in one case Rafael J. Wysocki
2018-02-08 15:44 ` Andy Shevchenko
2018-02-08 15:48 ` Rafael J. Wysocki
2018-02-08 15:59 ` Andy Shevchenko
2018-02-08 16:05 ` Rafael J. Wysocki
2018-02-08 15:45 ` Rafael J. Wysocki
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=1518106383.22495.206.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=okaya@codeaurora.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sakari.ailus@linux.intel.com \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).