From: Greg KH <gregkh@linuxfoundation.org>
To: Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: aahringo@redhat.com, teigland@redhat.com,
skhan@linuxfoundation.org, gfs2@lists.linux.dev,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] fs/dlm: use scnprintf() in lockspace show funcs
Date: Mon, 16 Jun 2025 16:22:11 +0200 [thread overview]
Message-ID: <2025061659-sauciness-ravioli-ff59@gregkh> (raw)
In-Reply-To: <20250616103441.370330-1-pranav.tyagi03@gmail.com>
On Mon, Jun 16, 2025 at 04:04:41PM +0530, Pranav Tyagi wrote:
> Replace all snprintf() instances with scnprintf(). snprintf() returns
> the number of bytes that would have been written had there been enough
> space. For sysfs attributes, snprintf() should not be used for the
> show() method. Instead use scnprintf() which returns the number of
> bytes actually written.
>
> Signed-off-by: Pranav Tyagi <pranav.tyagi03@gmail.com>
> ---
> fs/dlm/config.c | 2 +-
> fs/dlm/lockspace.c | 8 ++++----
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/fs/dlm/config.c b/fs/dlm/config.c
> index a23fd524a6ee..10486a46a540 100644
> --- a/fs/dlm/config.c
> +++ b/fs/dlm/config.c
> @@ -185,7 +185,7 @@ static ssize_t cluster_##name##_store(struct config_item *item, \
> } \
> static ssize_t cluster_##name##_show(struct config_item *item, char *buf) \
> { \
> - return snprintf(buf, PAGE_SIZE, "%u\n", dlm_config.ci_##name); \
> + return scnprintf(buf, PAGE_SIZE, "%u\n", dlm_config.ci_##name); \
sysfs_emit() or no change at all please.
prev parent reply other threads:[~2025-06-16 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 10:34 [PATCH] fs/dlm: use scnprintf() in lockspace show funcs Pranav Tyagi
2025-06-16 14:22 ` Greg KH [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=2025061659-sauciness-ravioli-ff59@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aahringo@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=pranav.tyagi03@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=teigland@redhat.com \
/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