Re: [PATCH v6] soc: aspeed: lpc-snoop: Fix usercopy overflow in snoop_file_read
Andrew Jeffery <[email protected]> Wed, 17 Jun 2026 10:14:44 +0930
| Newsgroups | org.ozlabs.lists.linux-aspeed,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-hardening,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <b50b84b169b632200ca348971451baca83357c7b.camel@codeconstruct.com.au> |
On Tue, 2026-06-16 at 07:30 +0000, Karthikeyan KS wrote: > Hi Andrew, > > Happy to. Short version: ast2600-evb can't hit the SMP timing window, > so I reproduce each missing piece deliberately. The driver code under > test is unmodified -- only the stimulus and the post-race state are > injected. Stock qemu-system-arm (Debian 8.2.2), no QEMU changes. > > Three obstacles, and what I did about each: This looks like a lot of heavily LLM-assisted effort. Please review the relevant documentation, starting here: https://docs.kernel.org/process/submitting-patches.html#using-assisted-by I feel the testing strategy is pretty questionable. Any invariant violation is possible with that type of meddling. I was interested in whether you drove the interrupt sequence via emulated hardware. I asked because upstream qemu doesn't currently support the snoop device. In v3 you said: The issue was observed on physical AST2600 (dual-core Cortex-A7) in production under heavy POST code traffic during concurrent userspace reads. https://lore.kernel.org/all/[email protected]/ Is this true? What platform did you test with? Andrew