From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Denis Efremov <efremov@linux.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: Use scnprintf() instead of snprintf() in device show functions
Date: Sun, 21 Jun 2020 10:56:56 +0200 [thread overview]
Message-ID: <20200621085656.GA95977@kroah.com> (raw)
In-Reply-To: <20200620150529.18678-1-efremov@linux.com>
On Sat, Jun 20, 2020 at 06:05:29PM +0300, Denis Efremov wrote:
> >From Documentation/filesystems/sysfs.txt:
> - show() must not use snprintf() when formatting the value to be
> returned to user space. If you can guarantee that an overflow
> will never happen you can use sprintf() otherwise you must use
> scnprintf().
>
> The reason is that snprintf() returns the length the resulting string
> would be, assuming the data will fit into the destination array.
> scnprintf() returns the length of the string actually created in buf.
>
> device_show_{ulong,int,bool}() functions are reference implementation
> and should respect the kernel documentation.
Ok, but you are not following that documentation below, why not?
>
> Signed-off-by: Denis Efremov <efremov@linux.com>
> ---
>
> Actually, I don't know why snprintf() is used here initially. It looks
> safe to use sprintf().
>
> drivers/base/core.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index 67d39a90b45c..2815deb511fc 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -1472,7 +1472,7 @@ ssize_t device_show_ulong(struct device *dev,
> char *buf)
> {
> struct dev_ext_attribute *ea = to_ext_attr(attr);
> - return snprintf(buf, PAGE_SIZE, "%lx\n", *(unsigned long *)(ea->var));
> + return scnprintf(buf, PAGE_SIZE, "%lx\n", *(unsigned long *)(ea->var));
As the documentation states, these should just be sprintf(), if you
really want to change these.
As-is, these are also ok, there is no need to change.
thanks,
greg k-h
prev parent reply other threads:[~2020-06-21 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 15:05 [PATCH] driver core: Use scnprintf() instead of snprintf() in device show functions Denis Efremov
2020-06-21 8:56 ` Greg Kroah-Hartman [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=20200621085656.GA95977@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=efremov@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.