From: Joe Perches <joe@perches.com>
To: Denis Efremov <efremov@linux.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
Alex Dewar <alex.dewar90@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysfs: Add sysfs_emit to replace sprintf to PAGE_SIZE buffers.
Date: Sat, 29 Aug 2020 00:13:28 -0700 [thread overview]
Message-ID: <fe4de2e9f0a492e66b870cddbadb820e3459cc7a.camel@perches.com> (raw)
In-Reply-To: <c77e83a0-7587-3e07-81cb-6b185d1ce6aa@linux.com>
On Sat, 2020-08-29 at 09:59 +0300, Denis Efremov wrote:
> Hi,
>
> On 8/29/20 1:52 AM, Joe Perches wrote:
> > sprintf does not know the PAGE_SIZE maximum of the temporary buffer
> > used for outputting sysfs content requests and it's possible to
> > overrun the buffer length.
> >
> > Add a generic sysfs_emit mechanism that knows that the size of the
> > temporary buffer and ensures that no overrun is done.
> >
> > Signed-off-by: Joe Perches <joe@perches.com>
> > --- rK
>
> It could be a good idea to update the docs to, i.e.:
> https://www.kernel.org/doc/html/latest/filesystems/sysfs.html
Yes, thanks.
I have the below already, but Greg makes a sensible point
about the generic use of sysfs_emit for single values
which is ~95% of the actual uses, so likely there will be
two functions. Given the multiple thousand instances,
using 2 functions would be smaller overall object code
as well.
Perhaps:
sysfs_emit (for single value output)
sysfs_emit_at (or sysfs_emit_pos ? or some better name?)
int sysfs_emit(char *buf, const char *fmt, ...)
int sysfs_emit_at(char *buf, int pos, const char *fmt, ...)
or maybe use
int sysfs_emit_pos(char *buf, char *pos, const char *fmt, ...)
The multiple use emit_at with int as the 2nd parameter would
make the direct return easier than the char * which needs a
subtraction.
six of this/half dozen of that...
cheers...
---
Anyway, this will need updating, likely with better examples.
diff --git a/Documentation/filesystems/sysfs.rst b/Documentation/filesystems/sysfs.rst
index ab0f7795792b..13c7a86fa6c8 100644
--- a/Documentation/filesystems/sysfs.rst
+++ b/Documentation/filesystems/sysfs.rst
@@ -242,12 +242,9 @@ Other notes:
is 4096.
- show() methods should return the number of bytes printed into the
- buffer. This is the return value of scnprintf().
+ buffer. This is the return value of sysfs_emit().
-- 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().
+- show() methods should only use sysfs_emit to format output.
next prev parent reply other threads:[~2020-08-29 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 22:52 Joe Perches
2020-08-29 6:22 ` Greg Kroah-Hartman
2020-08-29 6:41 ` Joe Perches
2020-08-29 6:51 ` Greg Kroah-Hartman
2020-08-29 6:59 ` Denis Efremov
2020-08-29 7:13 ` Joe Perches [this message]
2020-08-29 21:53 ` Denis Efremov
2020-08-29 23:49 ` Joe Perches
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=fe4de2e9f0a492e66b870cddbadb820e3459cc7a.camel@perches.com \
--to=joe@perches.com \
--cc=alex.dewar90@gmail.com \
--cc=efremov@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=keescook@chromium.org \
--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
all inboxes | Powered by JetHome®