From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: Christian Brauner <brauner@kernel.org>,
syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
syzbot <syzbot@kernel.org>,
adrianhuang0701@gmail.com, akpm@linux-foundation.org,
kexinsun@smail.nju.edu.cn, oleg@redhat.com, peterz@infradead.org,
syzbot@lists.linux.dev, tglx@kernel.org,
Dmitry Vyukov <dvyukov@google.com>,
Marco Elver <elver@google.com>
Subject: Re: [PATCH] signal: clear JOBCTL_PENDING_MASK for caller in zap_other_threads()
Date: Thu, 21 May 2026 16:17:54 +0200 [thread overview]
Message-ID: <2026052159-conductor-suffice-4c81@gregkh> (raw)
In-Reply-To: <CANp29Y5Cjy6k2vLp2+2O9FXwRXAmNP_ja6seORVXVQnrdUwH3g@mail.gmail.com>
On Thu, May 21, 2026 at 03:03:35PM +0200, Aleksandr Nogikh wrote:
> (+Greg)
>
> Hi Christian and Oleg,
>
> Thanks for reviewing and accepting the patch!
>
> However, it seems that we first need to clarify how these types of
> patches should be submitted to ensure we don't violate the Linux
> kernel rules regarding AI-assisted contributions.
The documentation is very clear on this, what is missing?
> In a discussion under another patch by syzbot [1], Greg noted that
> syzbot cannot be listed as the author. The official documentation [2]
> isn't very specific about how to handle this exact scenario.
A "tool" can not sign off on a patch. That's always been the case, a
person has to take ownership and responsibility for it from a legal and
technical point of view. Again, nothing new here, been this way for a
very long time.
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-21 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 9:05 [PATCH] signal: clear JOBCTL_PENDING_MASK for caller in zap_other_threads() syzbot
2026-05-21 12:22 ` Oleg Nesterov
2026-05-21 12:40 ` Christian Brauner
2026-05-21 13:03 ` Aleksandr Nogikh
2026-05-21 13:17 ` Christian Brauner
2026-05-21 14:32 ` Aleksandr Nogikh
2026-05-21 14:17 ` Greg Kroah-Hartman [this message]
2026-05-21 14:30 ` Aleksandr Nogikh
2026-05-21 15:00 ` Greg Kroah-Hartman
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=2026052159-conductor-suffice-4c81@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adrianhuang0701@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kexinsun@smail.nju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot@kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.