Re: Proposal: preflight checklist/lint for AI-assisted Linux kernel bug reports

Geert Uytterhoeven <[email protected]>
Newsgroups org.kernel.vger.workflows,org.kernel.linux.tools
Message-ID <CAMuHMdXmDj8iiYnMryWifEDqiP1XXQvxJq9U6EaJEP+j9RTeww@mail.gmail.com>
On Fri, 29 May 2026 at 15:09, mo to <[email protected]> wrote:
> I understand that AI-assisted vulnerability and bug reports have
> recently become a burden for kernel maintainers, especially when
> reports are duplicated, unverified, or lack enough technical detail to
> be actionable.
>
> I would like to suggest a lightweight “preflight” process for
> AI-assisted bug reports.
>
> The goal is not to replace the existing Linux kernel email workflow,
> nor to move kernel development into a web-based ticket system.
> Instead, the idea is to add a simple validation layer before a report
> reaches maintainers.
>
> For AI-assisted reports, the submitter could be required to include a
> structured checklist such as:
>
> AI-assisted bug report checklist:

Which of the below are not suitable for a non-AI-assisted bug report?

> - Kernel version:
> - Commit hash:
> - Architecture:
> - Kernel config:

Do you always need the full .config?

> - Affected subsystem / file / function:
> - Reproducer:
> - Reproduction rate:
> - Full dmesg / KASAN / UBSAN / lockdep / syzkaller log:

Ouch.

Fortunately I didn't do that when reporting 'thousands of "sync_state()
pending due to" and hundreds of "deferred probe pending" messages'...

> - Checked latest mainline: yes/no
> - Checked stable trees: yes/no
> - Checked lore.kernel.org for duplicates: yes/no

Definitely! Also for mere humans.
(Hi nvram mutex fixes ;-)

> - Existing patch found: yes/no
> - Why this is considered a security issue:
> - Impact assessment:
> - Suggested fix or mitigation:
> - Human verification performed: yes/no

Perhaps only yes should be permitted?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.