From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Roman Gushchin <roman.gushchin@linux.dev>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Derek Barbosa <debarbos@redhat.com>,
Matthieu Baerts <matttbe@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
users@kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Stephen Finucane <stephenfin@redhat.com>
Subject: Re: Linking Patchwork with Sashiko?
Date: Wed, 22 Jul 2026 01:46:42 +0300 [thread overview]
Message-ID: <20260721224642.GI536385@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20260721152501.0ff97e8c@gandalf.local.home>
On Tue, Jul 21, 2026 at 03:25:01PM -0400, Steven Rostedt wrote:
> On Tue, 21 Jul 2026 21:25:09 +0300 Laurent Pinchart wrote:
>
> > We've long known that we can't win if we treat security as a game of
> > whack-a-mole. Kees Cook and others have for years spent large mounts of
> > time and energy into securing the kernel by closing classes of
> > vulnerabilities. We've accepted a second programming language for kernel
> > development that should make memory-related bugs impossible in the first
> > place. In a less disruptive way, switching from C89 to C11 has enabled
> > features likes __free() that help make the code base safer.
> >
> > Do we need to act on security issues reported by LLMs ? For the time
> > being, surely. Is that enough ? No way. It's even more important today
> > than it used to be to make whole classes of bugs impossible in the first
> > place. The good news for people interested in that development is
> > there's lots of work to be done all across the kernel :-)
> >
> > Touting AI reviews as the solution to the security problem LLMs
> > generated in the first place without massively investing in kernel
> > hardening is in my opinion the real "putting our heads in the sand"
> > here.
>
> Who said the two are mutually exclusive? I believe there is still a large
> effort in hardening the kernel.
I certainly hope so :-)
> AI reviews is totally agnostic to that
> effort. Roman said at LSF/MM/BPF that he's the only one working on Sashikio
> at Google. Yes, Google is investing billions (if not trillions) of dollars
> into AI, but that has nothing to do with the Linux kernel. Roman has simply
> tapped into that effort to allow the Linux kernel to take advantage of that
> investment.
>
> It really sounds like you want companies to move effort from AI into the
> Linux kernel hardening. If Google did that, all it would do is move Roman
> from working on Sashiko to working on hardening the kernel. I think Roman
> is doing a hell of a lot more for the Linux kernel by staying with Sashiko!
As you said, it's not mutually exclusive. I'm sure Google has other
kernel developers than Roman.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-07-21 22:46 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260528144627.1ae09ff2@foz.lan>
[not found] ` <1372F826-5513-4EB2-AE27-1DC0D2DE0AEB@linux.dev>
[not found] ` <20260529083100.6710b6cd@foz.lan>
[not found] ` <20260529083801.2c7e8990@foz.lan>
[not found] ` <ahmwUk0uXTkdwohf@debarbos-thinkpadt14gen5.rmtusma.csb>
2026-05-30 8:30 ` Linking Patchwork with Sashiko? Mauro Carvalho Chehab
2026-05-30 15:57 ` Roman Gushchin
2026-05-30 18:00 ` Mauro Carvalho Chehab
2026-05-30 18:49 ` Mauro Carvalho Chehab
2026-05-30 18:53 ` Mauro Carvalho Chehab
2026-06-02 15:51 ` Derek Barbosa
2026-06-02 16:51 ` Mauro Carvalho Chehab
2026-06-02 18:39 ` Jason Gunthorpe
2026-06-02 20:29 ` Mauro Carvalho Chehab
2026-06-02 20:13 ` Roman Gushchin
2026-06-02 20:39 ` Mauro Carvalho Chehab
2026-06-02 20:44 ` Roman Gushchin
2026-06-02 23:50 ` Matthieu Baerts
2026-06-03 3:35 ` Mauro Carvalho Chehab
2026-06-03 3:49 ` Roman Gushchin
2026-06-04 6:52 ` Mauro Carvalho Chehab
2026-06-07 17:56 ` Mauro Carvalho Chehab
2026-06-30 20:32 ` Derek Barbosa
2026-07-10 5:45 ` Mauro Carvalho Chehab
2026-07-10 6:39 ` Mauro Carvalho Chehab
2026-07-11 1:01 ` Roman Gushchin
2026-07-13 7:55 ` Mauro Carvalho Chehab
2026-07-13 9:41 ` Laurent Pinchart
2026-07-13 20:04 ` Mauro Carvalho Chehab
2026-07-14 22:55 ` Roman Gushchin
2026-07-15 0:59 ` Laurent Pinchart
2026-07-15 2:00 ` Roman Gushchin
2026-07-15 3:06 ` Linus Torvalds
2026-07-15 12:21 ` Jori Koolstra
2026-07-15 16:50 ` Steven Rostedt
2026-07-15 18:13 ` Nicolas Dufresne
2026-07-15 19:12 ` Laurent Pinchart
2026-07-15 19:27 ` Nicolas Dufresne
2026-07-15 20:03 ` Laurent Pinchart
2026-07-16 15:04 ` August Zeller
2026-07-15 16:43 ` Laurent Pinchart
2026-07-15 23:28 ` lyude
2026-07-15 7:59 ` Jacopo Mondi
2026-07-15 8:40 ` Mauro Carvalho Chehab
2026-07-15 17:31 ` Theodore Tso
2026-07-16 8:07 ` Jacopo Mondi
2026-07-17 9:40 ` Paolo Bonzini
2026-07-17 12:20 ` Theodore Tso
2026-07-17 13:25 ` Mauro Carvalho Chehab
2026-07-20 13:55 ` Steven Rostedt
2026-07-20 14:26 ` Mark Brown
2026-07-20 18:24 ` Steven Rostedt
2026-07-21 16:42 ` Mark Brown
2026-07-21 19:15 ` Steven Rostedt
2026-07-21 17:12 ` Laurent Pinchart
2026-07-21 19:18 ` Steven Rostedt
2026-07-20 19:16 ` Mauro Carvalho Chehab
2026-07-21 15:43 ` Mauro Carvalho Chehab
2026-07-17 15:22 ` Nicolas Dufresne
2026-07-21 16:27 ` Laurent Pinchart
2026-07-15 12:38 ` Mark Brown
2026-07-15 16:28 ` Laurent Pinchart
2026-07-15 21:08 ` Roman Gushchin
2026-07-15 23:20 ` Steven Rostedt
2026-07-16 0:09 ` Roman Gushchin
2026-07-17 12:32 ` Laurent Pinchart
2026-07-20 18:08 ` Steven Rostedt
2026-07-21 18:25 ` Laurent Pinchart
2026-07-21 19:25 ` Steven Rostedt
2026-07-21 22:46 ` Laurent Pinchart [this message]
2026-07-21 23:41 ` Steven Rostedt
2026-07-15 3:54 ` Theodore Tso
2026-07-15 7:13 ` Mauro Carvalho Chehab
2026-07-15 12:42 ` James Bottomley
2026-07-15 16:18 ` Laurent Pinchart
2026-07-15 16:53 ` James Bottomley
2026-07-15 17:09 ` Laurent Pinchart
2026-07-15 16:11 ` Laurent Pinchart
2026-07-15 17:00 ` Jan Kara
2026-07-15 20:28 ` Laurent Pinchart
2026-07-15 20:36 ` James Bottomley
2026-07-15 20:42 ` Laurent Pinchart
2026-07-16 0:14 ` Roman Gushchin
2026-07-16 7:04 ` Mauro Carvalho Chehab
2026-07-15 23:32 ` Steven Rostedt
2026-07-16 0:03 ` Roman Gushchin
2026-07-21 16:01 ` Laurent Pinchart
2026-07-16 7:21 ` Mauro Carvalho Chehab
2026-07-16 13:33 ` Jan Kara
2026-07-21 22:43 ` Laurent Pinchart
2026-07-21 23:44 ` Steven Rostedt
2026-07-16 18:24 ` Willy Tarreau
2026-07-15 17:14 ` Theodore Tso
2026-07-15 17:35 ` Miguel Ojeda
2026-07-15 17:41 ` Laurent Pinchart
2026-07-15 18:18 ` Linus Torvalds
2026-07-15 18:51 ` Laurent Pinchart
2026-07-15 19:14 ` Linus Torvalds
2026-07-15 20:13 ` Laurent Pinchart
2026-07-16 9:20 ` Giacomo Tesio
2026-07-16 15:10 ` August Zeller
2026-07-16 20:54 ` Theodore Tso
2026-07-21 16:03 ` Laurent Pinchart
2026-07-15 16:28 ` Ihor Solodrai
2026-07-15 16:39 ` Laurent Pinchart
2026-07-15 17:12 ` Ihor Solodrai
2026-07-15 17:35 ` Mark Brown
2026-07-15 18:39 ` Ihor Solodrai
2026-07-15 20:32 ` Mark Brown
2026-07-15 19:06 ` Laurent Pinchart
2026-07-15 21:13 ` Theodore Tso
2026-07-16 3:00 ` Nicolas Dufresne
2026-07-16 3:53 ` Theodore Tso
2026-07-16 7:55 ` Mauro Carvalho Chehab
2026-07-16 20:54 ` Nicolas Dufresne
2026-07-16 22:30 ` Dmitry Torokhov
2026-07-16 6:23 ` Jai Luthra
2026-07-16 12:32 ` Theodore Tso
2026-07-15 17:41 ` Jason Gunthorpe
2026-07-15 19:10 ` Laurent Pinchart
2026-07-15 19:55 ` Mark Brown
2026-07-15 19:38 ` Dmitry Torokhov
2026-07-15 21:27 voste62ocr
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=20260721224642.GI536385@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=debarbos@redhat.com \
--cc=jgg@ziepe.ca \
--cc=konstantin@linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=stephenfin@redhat.com \
--cc=users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox