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: Avoid a potential useless over memory allocation in bch2_prt_vprintf()
Date: Tue, 19 Sep 2023 09:17:13 -0400 [thread overview]
Message-ID: <ZQmfWbIgPM0Oo8Jg@bfoster> (raw)
In-Reply-To: <0f40108bed3e084057223bdbe32c4b37f8500ff3.1694845203.git.christophe.jaillet@wanadoo.fr>
On Sat, Sep 16, 2023 at 08:20:24AM +0200, Christophe JAILLET wrote:
> printbuf_remaining() returns the number of characters we can print to the
> output buffer - i.e. excluding the terminating null.
>
> vsnprintf() takes the size of the buffer, including the trailing null
> space.
> It is truncated if the returned value is greater than or equal to the size
> of the buffer.
>
> Knowing all that, buffer sizes and overflow checks can be fixed in order
> to potentially avoid a useless memory over-allocation.
>
For whatever reason I had a hard time parsing this last sentence. Do
you mean to say there's an off by one here that leads to an unnecessary
overallocation?
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> Un-tested
> ---
> fs/bcachefs/printbuf.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/fs/bcachefs/printbuf.c b/fs/bcachefs/printbuf.c
> index de41f9a14492..77bee9060bfe 100644
> --- a/fs/bcachefs/printbuf.c
> +++ b/fs/bcachefs/printbuf.c
> @@ -54,8 +54,9 @@ void bch2_prt_vprintf(struct printbuf *out, const char *fmt, va_list args)
> va_list args2;
>
> va_copy(args2, args);
> - len = vsnprintf(out->buf + out->pos, printbuf_remaining(out), fmt, args2);
> - } while (len + 1 >= printbuf_remaining(out) &&
> + len = vsnprintf(out->buf + out->pos, printbuf_remaining(out) + 1,
> + fmt, args2);
> + } while (len >= printbuf_remaining(out) + 1 &&
> !bch2_printbuf_make_room(out, len + 1));
It's amazing how simple arithmetic can make my eyes cross at times. :) I
think I follow the fix after reading the commit log a couple times, but
could we use printbuf_remaining_size() appropriately in these places
that want to check actual buffer size (i.e. including terminating null)
instead of doing the manual size fixup?
Brian
>
> len = min_t(size_t, len,
> @@ -70,9 +71,10 @@ void bch2_prt_printf(struct printbuf *out, const char *fmt, ...)
>
> do {
> va_start(args, fmt);
> - len = vsnprintf(out->buf + out->pos, printbuf_remaining(out), fmt, args);
> + len = vsnprintf(out->buf + out->pos, printbuf_remaining(out) + 1,
> + fmt, args);
> va_end(args);
> - } while (len + 1 >= printbuf_remaining(out) &&
> + } while (len >= printbuf_remaining(out) + 1 &&
> !bch2_printbuf_make_room(out, len + 1));
>
> len = min_t(size_t, len,
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-09-19 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 6:20 [PATCH] bcachefs: Avoid a potential useless over memory allocation in bch2_prt_vprintf() Christophe JAILLET
2023-09-19 13:17 ` Brian Foster [this message]
2023-09-19 18:18 ` Christophe JAILLET
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=ZQmfWbIgPM0Oo8Jg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.