mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx+linux-hardening@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Kees Cook <kees@kernel.org>, Bill Wendling <morbo@google.com>,
	 "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	David Gow <david@davidgow.net>, Petr Mladek <pmladek@suse.com>,
	 Shuvam Pandey <shuvampandey1@gmail.com>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v5 06/12] seq_buf: Add seq_buf_strlen()
Date: Thu, 22 Oct 2026 22:11:27 +0200	[thread overview]
Message-ID: <atptYsHyS6YGtzPV@debian> (raw)
In-Reply-To: <20261022155726.7f20c4cb@gandalf.local.home>

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

Hi Steven,

> Date: 2026-10-22 15:57:51-0400
> From: Steven Rostedt <rostedt@goodmis.org>
>
> On Thu, 22 Oct 2026 21:41:53 +0200
> Alejandro Colomar <alx+linux-hardening@kernel.org> wrote:
> 
> > > > Hmm, I just realized that this could inadvertently overflow the buffer. If
> > > > len == size, it may not be overflowed. If using seq_buf_putmem() and
> > > > filling the entire buffer, calling this would force an overflow as we just
> > > > truncated the last byte.  
> > > 
> > > Hm, yes. So the "else" branch needs to include:
> > > 
> > > 	s->len = s->size + 1;  
> > 
> > Please think again about the possibility of using pointers instead of
> > lengths.  This is a source of off-by-one bugs that's only caused by
> > the choice of data, I believe.  If using pointers, truncation would be
> > stored as a NULL pointer, and off-by-ones would be less likely.
> > 
> > Consider this off-by-one to be just a sympthom of the underlying
> > problematic design.  Whenever a design forces you to write +1 or -1,
> > there are high chances that the design is sub-optimal regarding safety.
> 
> It's not an off-by-one error here. The s->len = size - 1 is correct, but it
> also has a side effect of removing a character without marking it
> overflowed.

It's correct, but at the same time an opportunity for off-by-one
mistakes.

> The seq_buf defines being "overflowed" as s->len == s->size + 1.
> What the else statement should have is:
> 
> 	else
> 		seq_buf_set_overflow(s);
> 
> Which would be less confusing to reviewers as that is defined as:
> 
> static inline void
> seq_buf_set_overflow(struct seq_buf *s)
> {
> 	s->len = s->size + 1;
> }

Agree.

But still, a better design would do:

	static inline void
	seq_buf_set_overflow(struct seq_buf *s)
	{
		s->p = NULL;
	}

This is way more robust, and also easier to understand.  My head is
boiling when trying to review this patch set for correctness.  That's
not a good sign.


Have a lovely night!
Alex

> 
> -- Steve

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2026-10-22 20:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 15:56 [PATCH v5 00/12] " Kees Cook
2026-10-05 15:56 ` [PATCH v5 01/12] seq_buf: Do not print an empty line from an overflowed seq_buf_do_printk() Kees Cook
2026-10-16 18:28   ` Steven Rostedt
2026-10-05 15:56 ` [PATCH v5 02/12] seq_buf: Do not pop from an overflowed seq_buf Kees Cook
2026-10-16 18:28   ` Steven Rostedt
2026-10-05 15:56 ` [PATCH v5 03/12] scsi: lpfc: Print rx monitor records straight into the seq_buf Kees Cook
2026-10-05 18:54   ` David Laight
2026-10-06 13:26     ` Kees Cook
2026-10-05 15:56 ` [PATCH v5 04/12] seq_buf: Copy what fits when seq_buf_puts() and seq_buf_putmem() overflow Kees Cook
2026-10-16 18:29   ` Steven Rostedt
2026-10-05 15:56 ` [PATCH v5 05/12] seq_buf: Clear what a writer did not claim when a seq_buf overflows Kees Cook
2026-10-05 18:59   ` David Laight
2026-10-06 21:26     ` Kees Cook
2026-10-16 18:43       ` Steven Rostedt
2026-10-16 18:35   ` Steven Rostedt
2026-10-05 15:56 ` [PATCH v5 06/12] seq_buf: Add seq_buf_strlen() Kees Cook
2026-10-16 18:59   ` Steven Rostedt
2026-10-22 18:06     ` Kees Cook
2026-10-22 19:41       ` Alejandro Colomar
2026-10-22 19:57         ` Steven Rostedt
2026-10-22 20:05           ` Steven Rostedt
2026-10-22 20:11           ` Alejandro Colomar [this message]
2026-10-22 20:20             ` Steven Rostedt
2026-10-22 20:38               ` Alejandro Colomar
2026-10-22 20:44                 ` Alejandro Colomar
2026-10-22 20:53                 ` Steven Rostedt
2026-10-22 21:02                   ` Alejandro Colomar
2026-10-05 15:56 ` [PATCH v5 07/12] seq_buf: Add seq_buf_terminate() Kees Cook
2026-10-05 15:56 ` [PATCH v5 08/12] bpf: Remove dead newline stripping from format_disasm_line() Kees Cook
2026-10-05 15:56 ` [PATCH v5 09/12] seq_buf: Add seq_buf_init_append() Kees Cook
2026-10-16 19:09   ` Steven Rostedt
2026-10-05 15:57 ` [PATCH v5 10/12] powerpc/papr_scm: Return the string length from the sysfs show functions Kees Cook
2026-10-05 15:57 ` [PATCH v5 11/12] nvdimm: ndtest: Return the string length from flags_show() Kees Cook
2026-10-05 15:57 ` [PATCH v5 12/12] docs: core-api: Document the seq_buf API Kees Cook
2026-10-16 19:13   ` Steven Rostedt
2026-10-12  5:00 ` [PATCH v5 00/12] seq_buf: Add seq_buf_strlen() Kees Cook

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=atptYsHyS6YGtzPV@debian \
    --to=alx+linux-hardening@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=david@davidgow.net \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morbo@google.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®