From: Jeff Layton <jlayton@kernel.org>
To: Krzysztof Karas <krzysztof.karas@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Qasim Ijaz <qasdev00@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v12 04/10] ref_tracker: have callers pass output function to pr_ostream()
Date: Fri, 30 May 2025 07:47:00 -0400 [thread overview]
Message-ID: <ee3f6fdb27820654c83cdac9df09e0fe6e43883f.camel@kernel.org> (raw)
In-Reply-To: <vzuwl22qfx5pkcgliy3n76mqx4od2dtbduga4wl4tlvtae63e3@vnzosrktvg5m>
On Fri, 2025-05-30 at 11:13 +0000, Krzysztof Karas wrote:
> Hi Jeff,
>
> [...]
> > +static void __ostream_printf pr_ostream_buf(struct ostream *stream, char *fmt, ...)
> > +{
> > + int ret, len = stream->size - stream->used;
> > + va_list args;
> > +
> > + va_start(args, fmt);
> > + ret = vsnprintf(stream->buf + stream->used, len, fmt, args);
> vsnprintf() technically may return a negative error code.
> In that case, we'd be adding some unwanted values to the
> stream->used. When we encounter an error we could skip
> modifying that field.
>
> > + va_end(args);
> > + stream->used += min(ret, len);
> > +}
> > +
> [...]
>
Good catch. I'll change this to be:
va_start(args, fmt);
ret = vsnprintf(stream->buf + stream->used, len, fmt, args);
va_end(args);
if (ret > 0)
stream->used += min(ret, len);
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-05-30 11:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 15:20 [PATCH v12 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir Jeff Layton
2025-05-29 15:20 ` [PATCH v12 01/10] i915: only initialize struct ref_tracker_dir once Jeff Layton
2025-05-30 11:01 ` Krzysztof Karas
2025-05-30 11:39 ` Jeff Layton
2025-05-29 15:20 ` [PATCH v12 02/10] ref_tracker: don't use %pK in pr_ostream() output Jeff Layton
2025-05-30 11:03 ` Krzysztof Karas
2025-05-29 15:20 ` [PATCH v12 03/10] ref_tracker: add a top level debugfs directory for ref_tracker Jeff Layton
2025-05-30 11:05 ` Krzysztof Karas
2025-06-04 9:12 ` Jani Nikula
2025-06-09 18:10 ` Jeff Layton
2025-05-29 15:20 ` [PATCH v12 04/10] ref_tracker: have callers pass output function to pr_ostream() Jeff Layton
2025-05-30 11:13 ` Krzysztof Karas
2025-05-30 11:47 ` Jeff Layton [this message]
2025-05-29 15:20 ` [PATCH v12 05/10] ref_tracker: add a static classname string to each ref_tracker_dir Jeff Layton
2025-05-29 15:20 ` [PATCH v12 06/10] ref_tracker: allow pr_ostream() to print directly to a seq_file Jeff Layton
2025-05-29 15:20 ` [PATCH v12 07/10] ref_tracker: automatically register a file in debugfs for a ref_tracker_dir Jeff Layton
2025-05-29 15:20 ` [PATCH v12 08/10] ref_tracker: add a way to create a symlink to the ref_tracker_dir debugfs file Jeff Layton
2025-05-29 15:20 ` [PATCH v12 09/10] net: add symlinks to ref_tracker_dir for netns Jeff Layton
2025-05-29 15:20 ` [PATCH v12 10/10] ref_tracker: eliminate the ref_tracker_dir name field Jeff Layton
2025-05-29 23:24 ` [PATCH v12 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir Jakub Kicinski
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=ee3f6fdb27820654c83cdac9df09e0fe6e43883f.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qasdev00@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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).