On Fri, 17 Feb 2023, Stan Johnson wrote:
> > What's interesting to me is that although there are stack smashing > errors and "aborted" messages during boot, nothing seems to have > actually failed or aborted (note that no processes are named as > "terminated" or "aborted" in the messages). Initscripts do a lot of "if grep -q" and "this || that" etc. Since a failure is normal, how would you tell that a process got aborted? > Once logged in, I can't duplicate the stack smashing (yet), and I don't > see random executables failing. The stack smashing seems to happen only > in startup scripts that have heavy access to /proc (the mountkernfs > script seems particularly vulnerable, as I recall), though none of the > scripts seems to actually fail. > Yes. We've seen processes started from initscripts crash when accessing /proc before. It was never debugged, though it wasn't a stack smashing error at the time. > I'm not a programmer, but I'm willing to learn. I don't know what > Debian's build environment is, or how to adopt it or set it up, but I > can look into it with some suggestions. As I understand it, Debian/m68k SID is built in Debian/m68k SID in QEMU. Please see, https://lists.debian.org/debian-68k/2023/02/msg00025.html
