From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Yu, Lang" <Lang.Yu@amd.com>
Cc: Joe Perches <joe@perches.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sysfs: Remove page boundary align limitation on sysfs_emit and sysfs_emit_at
Date: Thu, 9 Sep 2021 07:34:31 +0200 [thread overview]
Message-ID: <YTmc53ZPdDfC4+lz@kroah.com> (raw)
In-Reply-To: <DM6PR12MB425005AE652C12F04E66B5B8FBD59@DM6PR12MB4250.namprd12.prod.outlook.com>
On Thu, Sep 09, 2021 at 05:27:49AM +0000, Yu, Lang wrote:
> [AMD Official Use Only]
>
>
>
> >-----Original Message-----
> >From: Joe Perches <joe@perches.com>
> >Sent: Thursday, September 9, 2021 1:06 PM
> >To: Yu, Lang <Lang.Yu@amd.com>; Greg Kroah-Hartman
> ><gregkh@linuxfoundation.org>; Rafael J . Wysocki <rafael@kernel.org>; linux-
> >kernel@vger.kernel.org
> >Subject: Re: [PATCH] sysfs: Remove page boundary align limitation on sysfs_emit
> >and sysfs_emit_at
> >
> >On Wed, 2021-09-08 at 20:07 +0800, Lang Yu wrote:
> >> The key purpose of sysfs_emit and sysfs_emit_at is to ensure that no
> >> overrun is done. Make them more equivalent with scnprintf.
> >
> >I can't think of a single reason to do this.
> >sysfs_emit and sysfs_emit_at are specific to sysfs.
> >
> >Use of these functions outside of sysfs is not desired or supported.
> >
> >
> Thanks for your reply. But I'm still curious why you put such a limitation.
> As "Documentation/filesystems/sysfs.rst" described, we can just use
> scnprintf(buf, PAGE_SIZE, "%s\n", dev->name) in show functions without
> such a limitation.
>
> But you said that " - show() should only use sysfs_emit() or sysfs_emit_at() when formatting
> the value to be returned to user space. " in Documentation/filesystems/sysfs.rst.
>
> Some guys just try to replace scnprintf with sysfs_emit() or sysfs_emit_at() per above documents.
That is just fine in sysfs show() functions.
> But sprintf and sysfs_emit/sysfs_emit_at are not totally equivalent(e.g., page boundary align).
Which is good, it checks for more error conditions.
I fail to understand what problem you have had with this. What sysfs
file was converted and had issues?
> In my opinion, we add a new api and try to replace an old api. Does we need to make it more
> compatible with old api? Thanks.
There is no "old api" here. People used a wide variety of different
things in sysfs file show() functions, now you can just use a single
one.
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-09 5:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 12:07 [PATCH] sysfs: Remove page boundary align limitation on sysfs_emit and sysfs_emit_at Lang Yu
2021-09-08 12:32 ` Greg Kroah-Hartman
2021-09-08 12:52 ` Yu, Lang
2021-09-08 13:04 ` Greg Kroah-Hartman
2021-09-08 13:21 ` Yu, Lang
2021-09-08 13:49 ` Greg Kroah-Hartman
2021-09-08 15:33 ` Yu, Lang
2021-09-09 5:19 ` Greg Kroah-Hartman
2021-09-09 5:31 ` Yu, Lang
2021-09-09 6:05 ` Greg Kroah-Hartman
2021-09-09 5:05 ` Joe Perches
2021-09-09 5:27 ` Yu, Lang
2021-09-09 5:34 ` Greg Kroah-Hartman [this message]
2021-09-09 5:59 ` Yu, Lang
2021-09-09 6:07 ` Greg Kroah-Hartman
2021-09-09 5:44 ` Joe Perches
2021-09-09 5:52 ` Yu, Lang
2021-09-09 6:07 ` Greg Kroah-Hartman
2021-09-09 6:22 ` Yu, Lang
2021-09-09 6:35 ` Greg Kroah-Hartman
2021-09-09 7:48 ` Yu, Lang
2021-09-09 7:59 ` Greg Kroah-Hartman
2021-09-09 8:48 ` Yu, Lang
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=YTmc53ZPdDfC4+lz@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Lang.Yu@amd.com \
--cc=joe@perches.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox