On Fri, 17 Feb 2023, Stan Johnson wrote:
> On 2/17/23 4:24 PM, Finn Thain wrote: > > > > 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. > > Maybe the 68030 handles memory differently than the 68040? As I > mentioned previously, if there is a 68030 Mac emulator that can boot > Linux, then I could try that. I could also try running QEMU on a slow > x86 host to see if a slow client combined with the rapid accesses to > /proc from the scripts might be causing an issue, I suspect if the 68040 > were vulnerable to this problem, we'd be seeing it in QEMU. I'll check > this weekend to see whether QEMU is still not seeing any problem with my > latest kernel builds together with the latest Debian SID. > > And no, I likely won't be fixing anything, but perhaps I can report the > problem to the maintainers of the relevant package. And I will likely > choose (for my own systems) to keep back the last good userland binary > to prevent it from being overwritten until a fix is found. > Good luck with that.
