From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] ACPI: bus: Avoid non-ACPI device objects in walks over children
Date: Fri, 22 Apr 2022 18:26:10 +0300 [thread overview]
Message-ID: <YmLJEtDFhc3HFg3/@lahna> (raw)
In-Reply-To: <11974495.O9o76ZdvQC@kreacher>
Hi Rafael,
On Fri, Apr 22, 2022 at 05:13:48PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> When walking the children of an ACPI device, take extra care to avoid
> using to_acpi_device() on the ones that are not ACPI devices, because
> that may lead to out-of-bounds access and memory corruption.
>
> While at it, make the function passed to acpi_dev_for_each_child()
> take a struct acpi_device pointer argument (instead of a struct device
> one), so it is more straightforward to use.
>
> Fixes: b7dd6298db81 ("ACPI: PM: Introduce acpi_dev_power_up_children_with_adr()")
> Reported-by: kernel test robot <oliver.sang@intel.com>
> BugLink: https://lore.kernel.org/lkml/20220420064725.GB16310@xsang-OptiPlex-9020/
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
>
> The commit being fixed is present in linux-next.
>
> ---
> drivers/acpi/bus.c | 24 ++++++++++++++++++++++--
> drivers/acpi/device_pm.c | 5 +----
> include/acpi/acpi_bus.h | 2 +-
> 3 files changed, 24 insertions(+), 7 deletions(-)
>
> Index: linux-pm/drivers/acpi/bus.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/bus.c
> +++ linux-pm/drivers/acpi/bus.c
> @@ -1070,10 +1070,30 @@ int acpi_bus_for_each_dev(int (*fn)(stru
> }
> EXPORT_SYMBOL_GPL(acpi_bus_for_each_dev);
>
> +struct acpi_dev_walk_context {
> + int (*fn)(struct acpi_device *, void *);
> + void *data;
> +};
> +
> +static int acpi_dev_for_one_check(struct device *dev, void *context)
> +{
> + struct acpi_dev_walk_context *adwc = context;
> +
> + if (dev->bus != &acpi_bus_type)
> + return 0;
I wonder if it make sense to add dev_is_acpi() that does the above
analoguos to dev_is_pci()?
Regardless of that,
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2022-04-22 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 15:13 [PATCH] ACPI: bus: Avoid non-ACPI device objects in walks over children Rafael J. Wysocki
2022-04-22 15:26 ` Mika Westerberg [this message]
2022-04-22 16:00 ` 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=YmLJEtDFhc3HFg3/@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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