From: Jarkko Sakkinen <jarkko@kernel.org>
To: Sinan Turunc <enscrpt@pm.me>
Cc: David Howells <dhowells@redhat.com>,
paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] keys: serialise key instantiation against keyctl_chown_key()
Date: Tue, 17 Nov 2026 14:52:41 +0200 [thread overview]
Message-ID: <avxOGQOBm5p24nzQ@kernel.org> (raw)
In-Reply-To: <avxNd7uCbLiUAi3A@kernel.org>
On Tue, Nov 17, 2026 at 02:50:03PM +0200, Jarkko Sakkinen wrote:
> > An AI tool assisted with finding the race, writing the four-line fix and
> > the reproducer, and running the tests. I reviewed the kernel source and the
> > test logs and wrote this commit message myself.
>
> Irrelevant in the commit message as metaphorically it is now a tool just
> like text editor is a tool.
>
> I can write a horrific 4chan post with a text editor but if I send it to
> LKML and call it a kernel patch, I don't make claims that it was assisted
> by a text editor and reviewed by me.
>
> But yeah, I get the commit message better now, thank you.
And on softer side: making a mistake is not a mistake ;-)
This is all about standing behind whatever you submit; not so much about
"performance". I make mistakes all the time.
Br, Jarkko
prev parent reply other threads:[~2026-11-17 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 12:34 [PATCH v2] keys: serialise key instantiation against keyctl_chown_key() Sinan Turunc
2026-11-17 12:49 ` Jarkko Sakkinen
2026-11-17 12:52 ` Jarkko Sakkinen [this message]
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=avxOGQOBm5p24nzQ@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=enscrpt@pm.me \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.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