From: Brian Foster <bfoster@redhat.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-bcachefs@vger.kernel.org
Subject: Re: [PATCH] bcachefs: Use snprintf() instead of scnprintf() when appropriate
Date: Tue, 19 Sep 2023 09:17:27 -0400 [thread overview]
Message-ID: <ZQmfZ/nPMgiJK9eW@bfoster> (raw)
In-Reply-To: <9a998be3e2dbedcd3a9eae5f81ae6dcc6c0f98c4.1694849375.git.christophe.jaillet@wanadoo.fr>
On Sat, Sep 16, 2023 at 09:30:19AM +0200, Christophe JAILLET wrote:
> snprintf() and scnprintf() are the same, except for the returned value.
> When this value is not used, it is more logical to use snprintf() which is
> slightly simpler.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
Seems reasonable:
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/bcachefs/super.c | 2 +-
> fs/bcachefs/tests.c | 2 +-
> fs/bcachefs/trace.h | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/bcachefs/super.c b/fs/bcachefs/super.c
> index 2990eed85adf..773ea93e44c1 100644
> --- a/fs/bcachefs/super.c
> +++ b/fs/bcachefs/super.c
> @@ -1180,7 +1180,7 @@ static void bch2_dev_attach(struct bch_fs *c, struct bch_dev *ca,
> {
> ca->dev_idx = dev_idx;
> __set_bit(ca->dev_idx, ca->self.d);
> - scnprintf(ca->name, sizeof(ca->name), "dev-%u", dev_idx);
> + snprintf(ca->name, sizeof(ca->name), "dev-%u", dev_idx);
>
> ca->fs = c;
> rcu_assign_pointer(c->devs[ca->dev_idx], ca);
> diff --git a/fs/bcachefs/tests.c b/fs/bcachefs/tests.c
> index c907b3e00176..72f9bf186f9c 100644
> --- a/fs/bcachefs/tests.c
> +++ b/fs/bcachefs/tests.c
> @@ -926,7 +926,7 @@ int bch2_btree_perf_test(struct bch_fs *c, const char *testname,
>
> time = j.finish - j.start;
>
> - scnprintf(name_buf, sizeof(name_buf), "%s:", testname);
> + snprintf(name_buf, sizeof(name_buf), "%s:", testname);
> prt_human_readable_u64(&nr_buf, nr);
> prt_human_readable_u64(&per_sec_buf, div64_u64(nr * NSEC_PER_SEC, time));
> printk(KERN_INFO "%-12s %s with %u threads in %5llu sec, %5llu nsec per iter, %5s per sec\n",
> diff --git a/fs/bcachefs/trace.h b/fs/bcachefs/trace.h
> index 19264492151b..da303dd4b71c 100644
> --- a/fs/bcachefs/trace.h
> +++ b/fs/bcachefs/trace.h
> @@ -450,7 +450,7 @@ TRACE_EVENT(btree_path_relock_fail,
> c = six_lock_counts(&path->l[level].b->c.lock);
> __entry->read_count = c.n[SIX_LOCK_read];
> __entry->intent_count = c.n[SIX_LOCK_intent];
> - scnprintf(__entry->node, sizeof(__entry->node), "%px", b);
> + snprintf(__entry->node, sizeof(__entry->node), "%px", b);
> }
> __entry->iter_lock_seq = path->l[level].lock_seq;
> __entry->node_lock_seq = is_btree_node(path, level)
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-09-19 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 7:30 [PATCH] bcachefs: Use snprintf() instead of scnprintf() when appropriate Christophe JAILLET
2023-09-19 13:17 ` Brian Foster [this message]
2023-09-19 19:02 ` Kent Overstreet
2023-09-19 19:23 ` Christophe JAILLET
2023-09-20 0:38 ` Kent Overstreet
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=ZQmfZ/nPMgiJK9eW@bfoster \
--to=bfoster@redhat.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kent.overstreet@linux.dev \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.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