From: Andrew Lunn <andrew@lunn.ch>
To: Yuan Tan <yuantan098@gmail.com>
Cc: linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
jhs@mojatatu.com, gregkh@linuxfoundation.org, sven@narfation.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [RFC] VEGA: a syzbot-like workflow for LLM-found kernel bugs
Date: Wed, 8 Jul 2026 16:07:08 +0200 [thread overview]
Message-ID: <b392a243-7fc2-4fb6-a264-ba1e01891e30@lunn.ch> (raw)
In-Reply-To: <20260708092247.4188498-1-yuantan098@gmail.com>
> The rough idea
> ==============
>
> VEGA would have a public dashboard, similar to syzbot, and would
> send selected bug reports to the relevant kernel mailing lists.
>
> The goal is to send reports that contain enough information for maintainers
> or other developers to pick up, understand, reproduce and fix the issue.
>
> For each public report, we expect to include:
>
> - a description of the bug
> - the tested kernel tree and commit
> - the kernel config and environment
> - the crash log
> - a minimized user-space reproducer
> - the suspected introducing commit
> - a suggested fix patch
It would be nice if you could try to parse the git logs for the driver
and extrapolate its age, and if it is still being actively Maintained
by somebody.
We see lots of LLM generated patches for theoretical bugs, mostly in
error paths, for drivers which are EOL, and it is unlikely anybody is
still using the hardware. Such patches waste Reviewer/Maintainer time.
Maybe even make this part of your triage process. Prioritise issues
found on newer, used drivers, over old likely unused drives.
Andrew
next prev parent reply other threads:[~2026-07-08 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 9:22 [RFC] VEGA: a syzbot-like workflow for LLM-found kernel bugs Yuan Tan
2026-07-08 9:58 ` Paolo Abeni
2026-07-08 10:47 ` Laurent Pinchart
2026-07-08 12:24 ` Hillf Danton
2026-07-08 14:07 ` Andrew Lunn [this message]
2026-07-08 14:55 ` Greg KH
2026-07-11 2:14 ` Yuan Tan
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=b392a243-7fc2-4fb6-a264-ba1e01891e30@lunn.ch \
--to=andrew@lunn.ch \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sven@narfation.org \
--cc=workflows@vger.kernel.org \
--cc=yuantan098@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