From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: sashiko-reviews@lists.linux.dev, Chris Mason <clm@fb.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-scsi@vger.kernel.org, ksummit@lists.linux.dev
Subject: Re: How to fix problems with the sashiko review model
Date: Wed, 22 Jul 2026 09:45:48 -0400 [thread overview]
Message-ID: <ed0f74db3342ead9a36a0367b8a5cf694b0decf3.camel@HansenPartnership.com> (raw)
In-Reply-To: <2026072205-unsealed-emcee-b243@gregkh>
On Wed, 2026-07-22 at 15:10 +0200, Greg KH wrote:
[...]
> Also, this should be in the in-kernel documentation so the LLMs in
> general don't start sending us "fixes" for things that we don't want
> declared as a security issue. We've done this already for some things
> in the "threat model" file, so perhaps put it there? Then there's
> no need to add it to the github repo.
So you're thinking of this file:
Documentation/process/threat-model.rst
? It's already mostly in there, it's just that sashiko doesn't seem to
be picking it up (otherwise it wouldn't have suggested the problem I
noted), which is why I was thinking it needed to be a direct prompt ...
unless the prompt should be to read that file?
Regards,
James
next prev parent reply other threads:[~2026-07-22 13:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260722041257.1557-1-pengpeng@iscas.ac.cn>
[not found] ` <20260722042744.5C1B01F000E9@smtp.kernel.org>
2026-07-22 11:58 ` How to fix problems with the sashiko review model James Bottomley
2026-07-22 12:11 ` Laurent Pinchart
2026-07-22 12:42 ` James Bottomley
2026-07-22 13:08 ` Greg KH
2026-07-22 13:10 ` Greg KH
2026-07-22 13:45 ` James Bottomley [this message]
2026-07-22 14:08 ` Theodore Tso
2026-07-22 15:29 ` Miguel Ojeda
2026-07-22 13:42 ` James Bottomley
2026-07-22 14:00 ` Johannes Berg
2026-07-22 14:17 ` James Bottomley
2026-07-22 14:25 ` Johannes Berg
2026-07-22 15:39 ` Steven Rostedt
2026-07-22 15:55 ` James Bottomley
2026-07-22 16:36 ` Johannes Berg
2026-07-22 15:09 ` Mauro Carvalho Chehab
2026-07-22 15:24 ` James Bottomley
2026-07-22 20:25 ` Mauro Carvalho Chehab
2026-07-22 14:20 ` Mark Brown
2026-07-22 13:43 ` Guenter Roeck
2026-07-22 15:10 ` James Bottomley
2026-07-22 15:41 ` Miguel Ojeda
2026-07-22 15:54 ` Arnaldo Carvalho de Melo
2026-07-22 16:40 ` Roman Gushchin
2026-07-22 15:55 ` Roman Gushchin
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=ed0f74db3342ead9a36a0367b8a5cf694b0decf3.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=clm@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-scsi@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
/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