From: Hans de Goede <hdegoede@redhat.com>
To: Armin Wolf <W_Armin@gmx.de>, coproscefalo@gmail.com
Cc: ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/platform: toshiba_acpi: Fix array out-of-bounds access
Date: Wed, 10 Jul 2024 16:23:53 +0200 [thread overview]
Message-ID: <fdd8227d-4e72-4cac-9ab9-9b8a3de22f8e@redhat.com> (raw)
In-Reply-To: <20240709143851.10097-1-W_Armin@gmx.de>
Hi,
On 7/9/24 4:38 PM, Armin Wolf wrote:
> In order to use toshiba_dmi_quirks[] together with the standard DMI
> matching functions, it must be terminated by a empty entry.
>
> Since this entry is missing, an array out-of-bounds access occurs
> every time the quirk list is processed.
>
> Fix this by adding the terminating empty entry.
>
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202407091536.8b116b3d-lkp@intel.com
> Fixes: 3cb1f40dfdc3 ("drivers/platform: toshiba_acpi: Call HCI_PANEL_POWER_ON on resume on some models")
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
Thank you for your patch.
I have included this patch in the fixes pull-req to Linus
which I have just send out.
Regards,
Hans
> ---
> drivers/platform/x86/toshiba_acpi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/platform/x86/toshiba_acpi.c b/drivers/platform/x86/toshiba_acpi.c
> index 3a8d8df89186..d54bccec6ad6 100644
> --- a/drivers/platform/x86/toshiba_acpi.c
> +++ b/drivers/platform/x86/toshiba_acpi.c
> @@ -3299,6 +3299,7 @@ static const struct dmi_system_id toshiba_dmi_quirks[] = {
> },
> .driver_data = (void *)(QUIRK_TURN_ON_PANEL_ON_RESUME | QUIRK_HCI_HOTKEY_QUICKSTART),
> },
> + { }
> };
>
> static int toshiba_acpi_add(struct acpi_device *acpi_dev)
> --
> 2.39.2
>
prev parent reply other threads:[~2024-07-10 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 14:38 Armin Wolf
2024-07-10 14:23 ` Hans de Goede [this message]
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=fdd8227d-4e72-4cac-9ab9-9b8a3de22f8e@redhat.com \
--to=hdegoede@redhat.com \
--cc=W_Armin@gmx.de \
--cc=coproscefalo@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®