mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx+linux-hardening@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Alejandro Colomar <alx@kernel.org>,
	 Steven Rostedt <rostedt@goodmis.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	 Bill Wendling <morbo@google.com>, Petr Mladek <pmladek@suse.com>,
	 Randy Dunlap <rdunlap@infradead.org>,
	Shuvam Pandey <shuvampandey1@gmail.com>,
	 linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3] seq_buf: Mark a seq_buf overflowed when terminating it loses a byte
Date: Wed, 11 Nov 2026 00:35:30 +0100	[thread overview]
Message-ID: <avOp9udFzahnsmN_@devuan> (raw)
In-Reply-To: <20261110220716.37bfac-kees@kernel.org>

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

Hi Kees,

> Date: 2026-11-10 14:07:24-0800
> From: Kees Cook <kees@kernel.org>
>
> On Wed, Nov 04, 2026 at 12:28:27PM +0100, Alejandro Colomar wrote:
> > Please include:
> >
> > Cc: Alejandro Colomar <alx@kernel.org>
> > (or perhaps a second Reported-by.)
> 
> You were Cc'd. :)

Yup; what I meant is please store my name in the patch body, since
I want to be CCd if anyone looks at this patch in the future.  :)

> I try to avoid explicitly listing CCs in patch bodies,
> though I don't always manage to wrangle "git send-email" correctly.

Then a second Reported-by might be better there.


Cheers,
Alex

> 
> -Kees
> 
> -- 
> Kees Cook
> 

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

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

  reply	other threads:[~2026-11-10 23:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  3:31 Kees Cook
2026-11-04 11:17 ` Alejandro Colomar
2026-11-10 22:06   ` Kees Cook
2026-11-10 23:33     ` Alejandro Colomar
2026-11-04 11:28 ` Alejandro Colomar
2026-11-10 22:07   ` Kees Cook
2026-11-10 23:35     ` Alejandro Colomar [this message]
2026-11-04 13:40 ` Steven Rostedt

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=avOp9udFzahnsmN_@devuan \
    --to=alx+linux-hardening@kernel.org \
    --cc=alx@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --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=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=shuvampandey1@gmail.com \
    /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®