mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Bill Wendling <morbo@google.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Gow <david@davidgow.net>, Petr Mladek <pmladek@suse.com>,
	Shuvam Pandey <shuvampandey1@gmail.com>,
	nikitash.mariiaw@gmail.com, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2 5/9] seq_buf: Add seq_buf_strlen()
Date: Tue, 29 Sep 2026 19:31:12 -0700	[thread overview]
Message-ID: <202609291929.EF68AA59@keescook> (raw)
In-Reply-To: <20260921054647.3895bbb8@fedora>

On Mon, Sep 21, 2026 at 05:46:47AM -0400, Steven Rostedt wrote:
> That is, make this a separate patch to introduce a
> "seq_buf_terminate()" function as there's several places in the kernel
> that could replace seq_buf_str() with it.

My first reaction was that this would be redundant, since both
seq_buf_str() and seq_buf_strlen() terminate as a side effect and either
can be called for that alone. Then I went looking for the call sites
you meant, and yeah, it's pretty clear it's needed. Otherwise we're
depending on a side-effect and throwing away a return value:

        /* Terminate synthetic_name with a NUL. */
        seq_buf_str(&s);

And various other examples...

  kernel/trace/trace_events_hist.c:2992
  kernel/trace/trace_events_hist.c:3110
  kernel/trace/trace_events.c:4909
  kernel/trace/trace_events.c:4938
  kernel/bpf/diagnostics.c:354
  kernel/bpf/diagnostics.c:634
  kernel/bpf/diagnostics.c:638

I'll add it for v3.

-Kees

-- 
Kees Cook

  reply	other threads:[~2026-09-30  2:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19  0:26 [PATCH v2 0/9] " Kees Cook
2026-09-19  0:26 ` [PATCH v2 1/9] seq_buf: Do not print an empty line from an overflowed seq_buf_do_printk() Kees Cook
2026-09-19  0:27 ` [PATCH v2 2/9] seq_buf: Do not pop from an overflowed seq_buf Kees Cook
2026-09-19  0:27 ` [PATCH v2 3/9] seq_buf: Copy what fits when seq_buf_puts() and seq_buf_putmem() overflow Kees Cook
2026-09-19  0:27 ` [PATCH v2 4/9] seq_buf: Clear what a writer did not claim when a seq_buf overflows Kees Cook
2026-09-19  0:27 ` [PATCH v2 5/9] seq_buf: Add seq_buf_strlen() Kees Cook
2026-09-19  7:38   ` Greg KH
2026-09-19 21:15     ` Kees Cook
2026-09-20  5:34       ` Greg KH
2026-09-20  8:58         ` David Laight
2026-09-30  2:28         ` Kees Cook
2026-09-21  9:46   ` Steven Rostedt
2026-09-30  2:31     ` Kees Cook [this message]
2026-09-19  0:27 ` [PATCH v2 6/9] seq_buf: Add seq_buf_init_append() Kees Cook
2026-09-19  0:27 ` [PATCH v2 7/9] powerpc/papr_scm: Return the string length from the sysfs show functions Kees Cook
2026-09-19  0:27 ` [PATCH v2 8/9] nvdimm: ndtest: Return the string length from flags_show() Kees Cook
2026-09-19  0:27 ` [PATCH v2 9/9] docs: core-api: Document the seq_buf API Kees Cook
2026-09-19  1:54   ` Randy Dunlap

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=202609291929.EF68AA59@keescook \
    --to=kees@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=david@davidgow.net \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morbo@google.com \
    --cc=nikitash.mariiaw@gmail.com \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=shuvampandey1@gmail.com \
    --cc=willy@infradead.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

all inboxes | Powered by JetHome®