From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: prasanth.ksr@dell.com, Hans de Goede <hansg@kernel.org>,
divya.bharathi@dell.com, mario.limonciello@dell.com,
Dell.Client.Kernel@dell.com,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: dell-wmi-sysman: bound enumeration string aggregation
Date: Tue, 7 Apr 2026 17:19:49 +0300 (EEST) [thread overview]
Message-ID: <7a55f2f6-38dd-298a-d036-3e528f542c52@linux.intel.com> (raw)
In-Reply-To: <20260329030948.32467-1-pengpeng@iscas.ac.cn>
On Sun, 29 Mar 2026, Pengpeng Hou wrote:
> populate_enum_data() aggregates firmware-provided value-modifier and possible-value strings into fixed 512-byte struct members. The current code bounds each individual source string but then appends every string and separator with raw strcat() and no remaining-space check.
>
> Switch the aggregation loops to a bounded append helper and reject enumeration packages whose combined strings do not fit in the destination buffers.
Please fold changelog paragraphs to 72 chars.
> Fixes: e8a60aa7404b ("platform/x86: Introduce support for Systems Management Driver over WMI for Dell Systems")
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
> .../dell/dell-wmi-sysman/enum-attributes.c | 34 +++++++++++++++----
> 1 file changed, 28 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/platform/x86/dell/dell-wmi-sysman/enum-attributes.c b/drivers/platform/x86/dell/dell-wmi-sysman/enum-attributes.c
> index 09996fbdc707..14decb219128 100644
> --- a/drivers/platform/x86/dell/dell-wmi-sysman/enum-attributes.c
> +++ b/drivers/platform/x86/dell/dell-wmi-sysman/enum-attributes.c
> @@ -10,6 +10,26 @@
>
> get_instance_id(enumeration);
>
> +static int append_enum_string(char *dest, const char *src)
> +{
> + size_t dest_len = strlen(dest);
> + ssize_t copied;
> +
> + if (dest_len >= MAX_BUFF)
Doesn't this imply that something is already broken (buggy) if we blew
past the allocated buffer? If so, I suppose it would warrant
WARN_ON_ONCE() if something caused such invalid string in dest.
> + return -EINVAL;
> +
> + copied = strscpy(dest + dest_len, src, MAX_BUFF - dest_len);
> + if (copied < 0)
> + return -EINVAL;
> +
> + dest_len += copied;
> + copied = strscpy(dest + dest_len, ";", MAX_BUFF - dest_len);
> + if (copied < 0)
> + return -EINVAL;
> +
> + return 0;
> +}
> +
> static ssize_t current_value_show(struct kobject *kobj, struct kobj_attribute *attr, char *buf)
> {
> int instance_id = get_enumeration_instance_id(kobj);
> @@ -176,9 +196,10 @@ int populate_enum_data(union acpi_object *enumeration_obj, int instance_id,
> return -EINVAL;
> if (check_property_type(enumeration, next_obj, ACPI_TYPE_STRING))
> return -EINVAL;
> - strcat(wmi_priv.enumeration_data[instance_id].dell_value_modifier,
> - enumeration_obj[next_obj++].string.pointer);
> - strcat(wmi_priv.enumeration_data[instance_id].dell_value_modifier, ";");
> + if (append_enum_string(
> + wmi_priv.enumeration_data[instance_id].dell_value_modifier,
> + enumeration_obj[next_obj++].string.pointer))
> + return -EINVAL;
> }
>
> if (next_obj >= enum_property_count)
> @@ -193,9 +214,10 @@ int populate_enum_data(union acpi_object *enumeration_obj, int instance_id,
> return -EINVAL;
> if (check_property_type(enumeration, next_obj, ACPI_TYPE_STRING))
> return -EINVAL;
> - strcat(wmi_priv.enumeration_data[instance_id].possible_values,
> - enumeration_obj[next_obj++].string.pointer);
> - strcat(wmi_priv.enumeration_data[instance_id].possible_values, ";");
> + if (append_enum_string(
> + wmi_priv.enumeration_data[instance_id].possible_values,
> + enumeration_obj[next_obj++].string.pointer))
> + return -EINVAL;
> }
>
> return sysfs_create_group(attr_name_kobj, &enumeration_attr_group);
>
--
i.
next prev parent reply other threads:[~2026-04-07 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 3:09 Pengpeng Hou
2026-04-07 14:19 ` Ilpo Järvinen [this message]
2026-04-08 0:38 ` [PATCH v2] " Pengpeng Hou
2026-04-09 13:41 ` Ilpo Järvinen
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=7a55f2f6-38dd-298a-d036-3e528f542c52@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=divya.bharathi@dell.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=pengpeng@iscas.ac.cn \
--cc=platform-driver-x86@vger.kernel.org \
--cc=prasanth.ksr@dell.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®