mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Prasanth Ksr <prasanth.ksr@dell.com>,
	Hans de Goede <hansg@kernel.org>,
	 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: Use sysfs_emit{_at} in show functions
Date: Thu, 5 Mar 2026 14:48:22 +0200 (EET)	[thread overview]
Message-ID: <77f08627-cb28-8c0e-112b-f7ebef5a9a74@linux.intel.com> (raw)
In-Reply-To: <20260305124126.255026-2-thorsten.blum@linux.dev>

On Thu, 5 Mar 2026, Thorsten Blum wrote:

> Replace sprintf() with sysfs_emit() and sysfs_emit_at() in sysfs show
> functions. sysfs_emit() and sysfs_emit_at() are preferred for formatting
> sysfs output because they provide safer bounds checking.
> 
> In reset_bios_show(), use sysfs_emit_at() to avoid manual buffer size
> accounting.
> 
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
>  .../platform/x86/dell/dell-wmi-sysman/sysman.c | 18 ++++++++----------
>  1 file changed, 8 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/platform/x86/dell/dell-wmi-sysman/sysman.c b/drivers/platform/x86/dell/dell-wmi-sysman/sysman.c
> index 9dddab6c9397..0f24cecc93fc 100644
> --- a/drivers/platform/x86/dell/dell-wmi-sysman/sysman.c
> +++ b/drivers/platform/x86/dell/dell-wmi-sysman/sysman.c
> @@ -11,6 +11,7 @@
>  #include <linux/dmi.h>
>  #include <linux/module.h>
>  #include <linux/kernel.h>
> +#include <linux/sysfs.h>
>  #include <linux/wmi.h>
>  #include "dell-wmi-sysman.h"
>  #include "../../firmware_attributes_class.h"
> @@ -143,17 +144,14 @@ int map_wmi_error(int error_code)
>   */
>  static ssize_t reset_bios_show(struct kobject *kobj, struct kobj_attribute *attr, char *buf)
>  {
> -	char *start = buf;
> +	ssize_t len = 0;
>  	int i;
>  
> -	for (i = 0; i < MAX_TYPES; i++) {
> -		if (i == reset_option)
> -			buf += sprintf(buf, "[%s] ", reset_types[i]);
> -		else
> -			buf += sprintf(buf, "%s ", reset_types[i]);
> -	}
> -	buf += sprintf(buf, "\n");
> -	return buf-start;
> +	for (i = 0; i < MAX_TYPES; i++)
> +		len += sysfs_emit_at(buf, len, i == reset_option ? "[%s] " : "%s ",

Are all checkers okay with this construct? IIRC something doesn't 
like having such logic in where only a formatting string is expected.

--
 i.

> +				     reset_types[i]);
> +	len += sysfs_emit_at(buf, len, "\n");
> +	return len;
>  }
>  
>  /**
> @@ -194,7 +192,7 @@ static ssize_t reset_bios_store(struct kobject *kobj,
>  static ssize_t pending_reboot_show(struct kobject *kobj, struct kobj_attribute *attr,
>  				   char *buf)
>  {
> -	return sprintf(buf, "%d\n", wmi_priv.pending_changes);
> +	return sysfs_emit(buf, "%d\n", wmi_priv.pending_changes);
>  }
>  
>  static struct kobj_attribute reset_bios = __ATTR_RW(reset_bios);
> 

  reply	other threads:[~2026-03-05 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 12:41 Thorsten Blum
2026-03-05 12:48 ` Ilpo Järvinen [this message]
2026-03-05 13:00   ` Thorsten Blum
2026-03-05 13:10     ` 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=77f08627-cb28-8c0e-112b-f7ebef5a9a74@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=prasanth.ksr@dell.com \
    --cc=thorsten.blum@linux.dev \
    /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®