On Fri, 17 Feb 2023, Stan Johnson wrote:
> > The error could have been exposed in any package where > "-fstack-protector-strong" was recently added. > And if you find the last good userland binary, what then? Fix the bad userland binary? That's wonderful but it doesn't explain why the bad userland binary went undetected with Debian's kernel build. And it doesn't explain why you can't reproduce the problem in QEMU. Moreover, the above was always an unlikely scenario because an actual buffer overrun in a userland binary that only shows up on '030 is improbable in the first place, because code paths conditional on processor variant are normally found in the kernel. Hence the advice I gave 10 days ago.
