[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YfI6Qj+oIsNQYPJ2@kroah.com>
Date: Thu, 27 Jan 2022 07:22:58 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: davidcomponentone@...il.com
Cc: bhelgaas@...gle.com, yang.guang5@....com.cn, rajatja@...gle.com,
Thinh.Nguyen@...opsys.com, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, Zeal Robot <zealci@....com.cn>
Subject: Re: [PATCH] usb: core: replace snprintf with sysfs_emit
On Thu, Jan 27, 2022 at 07:54:54AM +0800, davidcomponentone@...il.com wrote:
> From: Yang Guang <yang.guang5@....com.cn>
>
> coccinelle report:
> ./drivers/usb/core/sysfs.c:921:8-16:
> WARNING: use scnprintf or sprintf
> ./drivers/usb/core/sysfs.c:730:8-16:
> WARNING: use scnprintf or sprintf
>
> Use sysfs_emit instead of scnprintf or sprintf makes more sense.
>
> Reported-by: Zeal Robot <zealci@....com.cn>
Again, no, this did not report this. I'll keep ignoring changes like
this that get this wrong.
> Signed-off-by: Yang Guang <yang.guang5@....com.cn>
> Signed-off-by: David Yang <davidcomponentone@...il.com>
> ---
> drivers/usb/core/sysfs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/core/sysfs.c b/drivers/usb/core/sysfs.c
> index fa2e49d432ff..6387c0dfe30e 100644
> --- a/drivers/usb/core/sysfs.c
> +++ b/drivers/usb/core/sysfs.c
> @@ -727,7 +727,7 @@ static ssize_t authorized_show(struct device *dev,
> struct device_attribute *attr, char *buf)
> {
> struct usb_device *usb_dev = to_usb_device(dev);
> - return snprintf(buf, PAGE_SIZE, "%u\n", usb_dev->authorized);
> + return sysfs_emit(buf, "%u\n", usb_dev->authorized);
> }
>
> /*
> @@ -918,7 +918,7 @@ static ssize_t authorized_default_show(struct device *dev,
> struct usb_hcd *hcd;
>
> hcd = bus_to_hcd(usb_bus);
> - return snprintf(buf, PAGE_SIZE, "%u\n", hcd->dev_policy);
> + return sysfs_emit(buf, "%u\n", hcd->dev_policy);
> }
>
> static ssize_t authorized_default_store(struct device *dev,
> --
> 2.30.2
>
Also this change is not correct, why are you only doing this for 2 sysfs
files and not all of them? Is there anything incorrect about the
current sysfs handling in this file that requires them to be changed to
use the new api?
greg k-h
Powered by blists - more mailing lists