From: Paolo Abeni <pabeni@redhat.com>
To: Yuan Tan <yuantan098@gmail.com>,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Cc: jhs@mojatatu.com, gregkh@linuxfoundation.org, sven@narfation.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-crypto@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [RFC] VEGA: a syzbot-like workflow for LLM-found kernel bugs
Date: Wed, 8 Jul 2026 11:58:06 +0200 [thread overview]
Message-ID: <e981a64f-ec3f-45d6-b20f-e03b61a91f2b@redhat.com> (raw)
In-Reply-To: <20260708092247.4188498-1-yuantan098@gmail.com>
Hi,
On 7/8/26 11:22 AM, Yuan Tan wrote:
> 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
>
> The suggested fix patch is meant to reduce maintainer burden. It still need
> human review, but hopefully it can save a lot time from building a patch
> from scratch.
Thanks for sharing. This sounds very interesting to me, modulo final
impact on the ML - overall load is severely increased since the LLM era,
while the maintainers pool not so much.
A few notes on top of my head:
- the amount/rate of reports is critical. The higher the rate, the
better need to be the reproducer and the suggested patch.
- the crash log should include the decoded stack trace.
- IIRC syzbot reports sharing is [always] human
moderated/limited/controlled. I think that is the correct default and I
hope it should be possible for you, too.
- it's not entirely clear to me who exactly is 'you' and would
appreciate more info about that.
- it would be great to discuss this topic in person, i.e. in the
upcoming NetDev.
Thanks,
Paolo
next prev parent reply other threads:[~2026-07-08 9:58 UTC|newest]
Thread overview: 6+ 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 [this message]
2026-07-08 10:47 ` Laurent Pinchart
2026-07-08 12:24 ` Hillf Danton
2026-07-08 14:07 ` Andrew Lunn
2026-07-08 14:55 ` Greg KH
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=e981a64f-ec3f-45d6-b20f-e03b61a91f2b@redhat.com \
--to=pabeni@redhat.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--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