From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alejandro Colomar <alx+linux-hardening@kernel.org>
Cc: Kees Cook <kees@kernel.org>, Alejandro Colomar <alx@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
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 10:49:59 +0200 [thread overview]
Message-ID: <avQsNwYvySgLM8A-@ashevche-desk.local> (raw)
In-Reply-To: <avOp9udFzahnsmN_@devuan>
On Wed, Nov 11, 2026 at 12:35:30AM +0100, Alejandro Colomar wrote:
> 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. :)
This can be done via `b4 trailers`. What is important in that case is to have
a Link tag.
Again, we have new tools, it will be nice to embrace them.
> > 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.
This will work.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-11-11 8:50 UTC|newest]
Thread overview: 11+ 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
2026-11-11 6:16 ` Kees Cook
2026-11-11 8:51 ` Andy Shevchenko
2026-11-11 8:49 ` Andy Shevchenko [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=avQsNwYvySgLM8A-@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=alx+linux-hardening@kernel.org \
--cc=alx@kernel.org \
--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®