On 2/17/23 3:38 PM, Finn Thain wrote: > On Fri, 17 Feb 2023, Stan Johnson wrote: > >> >> That's not to say a SIGABRT is ignored, it just doesn't kill PID 1. >> > > I doubt that /sbin/init is generating the "stack smashing detected" error > but you may need to modify it to find out. If you can't figure out which > userland binary is involved, you'll have to focus on your custom kernel > binary, just as I proposed in my message dated 8 Feb 2023. >
Yeah, I doubt it, too, since I removed "-fstack-protector-strong" from /sbin/init only and still got the messages. But I no longer think it's caused by the kernel, either, despite my custom options. I can still use your script to bisect the config file to bring it closer to Debian's config if necessary. Since the error isn't repeatable in QEMU, I want to limit the number of tests as much as possible. Determining whether it's related at all to sysvinit will be my first step. The error could have been exposed in any package where "-fstack-protector-strong" was recently added. If I can find the first-offending sysvinit, assuming there is one, then a command trace of each script may be helpful.
