Re: How to fix problems with the sashiko review model
Johannes Berg <[email protected]> Wed, 22 Jul 2026 16:00:15 +0200
| Newsgroups | dev.linux.lists.ksummit,dev.linux.lists.sashiko-reviews,org.kernel.vger.linux-scsi |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 2026-07-22 at 09:42 -0400, James Bottomley wrote: >=20 > Well, I noted that in my reply above. The way I was thinking of > implementing it was to add a general instruction file for drivers which > would make hardware trusted for pretty much everything and then > instruct the AI to consult driver specific files for overrides to this > so we could add the additional threat checks to usb.md and virt.md I guess it's a question which way around it should be - but I'll note that generally for wifi customers tend to not trust the "hardware" because it's mostly firmware, is generally buggy and can be attacked over the air too... Personally (with that background) I'd tend to lean towards saying the high-performance stuff that does want/need to trust the device should opt out, it's harder to get that wrong. If we generally opt out as you describe and then forgot to include something, we might have issues. johannes