Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Yuan Tan <yuantan098@gmail.com>
Cc: andrew@lunn.ch, Paolo Abeni <pabeni@redhat.com>,
	laurent.pinchart@ideasonboard.com, hdanton@sina.com,
	linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
	jhs@mojatatu.com, 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: Sat, 11 Jul 2026 07:33:42 +0200	[thread overview]
Message-ID: <2026071131-dweeb-quickstep-d550@gregkh> (raw)
In-Reply-To: <CAPuPA7Kdy_wghauOH5pggq+woLmtp4-BEyn8LoBJ2UhRExF+Xw@mail.gmail.com>

On Fri, Jul 10, 2026 at 07:14:36PM -0700, Yuan Tan wrote:
> > But hey, I could be totally wrong.  Maybe some generous company that is
> > involved in unleashing this hell on us would be so kind as to pony up to
> > do the work to create this and help fix the issues that their tools are
> > finding.  Just like Google did in the past, there is precedent, but for
> > some reason people don't like learning from history...
> 
> We have also received some bug bounty rewards from Google, which gives
> us some resources to put back into this effort.

That's good, but I don't want you to have to rely on Google's bug bounty
money, as that is not going to be reliable if past history is any
indication :(

> We are prepared to invest more engineering time in fixing these bugs,
> and we are also considering hiring engineers to help.
> 
> Will you also be attending NetDev in person? If so, perhaps we can chat there :)

Unfortunatly due to passport/visa issues, I can not attend this year,
but will be speaking remotely.  I will be in Prague later this year at
OSS and Plumbers.

thanks,

greg k-h

      reply	other threads:[~2026-07-11  5:33 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 14:07 ` Andrew Lunn
2026-07-08 14:55 ` Greg KH
2026-07-11  2:14   ` Yuan Tan
2026-07-11  5:33     ` Greg KH [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=2026071131-dweeb-quickstep-d550@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew@lunn.ch \
    --cc=hdanton@sina.com \
    --cc=jhs@mojatatu.com \
    --cc=laurent.pinchart@ideasonboard.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=pabeni@redhat.com \
    --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