From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-mm@kvack.org
Cc: Denis Efremov <efremov@linux.com>,
Julia Lawall <julia.lawall@inria.fr>,
Alex Dewar <alex.dewar90@gmail.com>,
linux-doc@vger.kernel.org
Subject: [PATCH V3 0/8] sysfs: drivers core: Add and use sysfs_emit and sysfs_emit_at
Date: Wed, 16 Sep 2020 13:40:37 -0700 [thread overview]
Message-ID: <cover.1600285923.git.joe@perches.com> (raw)
Output defects can exist in sysfs content using sprintf and snprintf.
sprintf does not know the PAGE_SIZE maximum of the temporary buffer
used for outputting sysfs content and it's possible to overrun the
PAGE_SIZE buffer length.
Add a generic sysfs_emit function that knows that the size of the
temporary buffer and ensures that no overrun is done.
Add a generic sysfs_emit_at function that can be used in multiple
call situations that also ensures that no overrun is done.
V2: Add drivers core conversions
V3: Add a few more neatenings and conversions to drivers core
Add mm hugetlb_report_node_meminfo conversion
Joe Perches (8):
sysfs: Add sysfs_emit and sysfs_emit_at to format sysfs output
drivers core: Use sysfs_emit and sysfs_emit_at for show(device *...) functions
drivers core: Remove strcat uses around sysfs_emit and neaten
drivers core: Reindent a couple uses around sysfs_emit
drivers core: Miscellaneous changes for sysfs_emit
mm: and drivers core: Convert hugetlb_report_node_meminfo to sysfs_emit
drivers core: Use sysfs_emit for shared_cpu_map_show and shared_cpu_list_show
drivers core: node: Use a more typical macro definition style for ACCESS_ATTR
Documentation/filesystems/sysfs.rst | 8 +-
drivers/base/arch_topology.c | 2 +-
drivers/base/bus.c | 2 +-
drivers/base/cacheinfo.c | 49 ++--
drivers/base/class.c | 2 +-
drivers/base/core.c | 59 +++--
drivers/base/cpu.c | 84 ++++---
drivers/base/dd.c | 3 +-
drivers/base/devcoredump.c | 2 +-
drivers/base/firmware_loader/fallback.c | 4 +-
drivers/base/memory.c | 62 ++---
drivers/base/node.c | 306 ++++++++++++------------
drivers/base/platform.c | 17 +-
drivers/base/power/sysfs.c | 160 ++++++++-----
drivers/base/power/wakeup_stats.c | 17 +-
drivers/base/soc.c | 64 +++--
drivers/base/topology.c | 10 +-
fs/sysfs/file.c | 55 +++++
include/linux/hugetlb.h | 4 +-
include/linux/sysfs.h | 15 ++
mm/hugetlb.c | 18 +-
21 files changed, 532 insertions(+), 411 deletions(-)
--
2.26.0
next reply other threads:[~2020-09-16 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 20:40 Joe Perches [this message]
2020-09-16 20:40 ` [PATCH V3 2/8] drivers core: Use sysfs_emit and sysfs_emit_at for show(device *...) functions Joe Perches
2020-09-16 20:40 ` [PATCH V3 3/8] drivers core: Remove strcat uses around sysfs_emit and neaten Joe Perches
2020-09-16 20:40 ` [PATCH V3 4/8] drivers core: Reindent a couple uses around sysfs_emit Joe Perches
2020-09-16 20:40 ` [PATCH V3 5/8] drivers core: Miscellaneous changes for sysfs_emit 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=cover.1600285923.git.joe@perches.com \
--to=joe@perches.com \
--cc=alex.dewar90@gmail.com \
--cc=efremov@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@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;
as well as URLs for NNTP newsgroup(s).