After I upgraded to glibc-2.29-r2 I get "stack smashing detected" errors in a lot of places, critical were these 2: -calling fsck during boot (it called fsck.ext*, which seems to work), these failures causes boot to fail -ssh login Also many of my remote nagios checks failed, I'm not entirely sure what caused this, but it could have been ssh client failing, too. After downgrading to 2.28-r6 things worked again immediately.
Sounds like a glibc bug. Is fsck a statically linked file by chance? I'd like to reproduce it in qemu-user or qemu-system and debug a bit. Wonder which binary would be easiest to debug.
Nope, fsck is dynamically linked.
I failed to reproduce it on defaults. Can you post full `emerge --info`? I'll try to reproduce locally with a closer to yours' environment.
Not sure what's going on here. I cannot reproduce. glibc-2.29-r2 looks good on catbus.
Let's close it as obsolete.