Created attachment 216711 [details] Possible fix Despite of strlcpy still planned for glibc[1], let's catch this case for extra safety. Apparently, some distributions have this already[2]. I know that we can't make it right here and right now, but at least we need to fix libcmd somehow to prevent this problem in the future. Maybe make an entry in uapi/linux/libc-compat.h? 1. https://sourceware.org/ml/libc-alpha/2016-01/msg00205.html 2. https://bugzilla.altlinux.org/32108 Attaching possible fix for this, not ideal, but it works for me.
Another iteration for strlcpy inclusion - https://sourceware.org/ml/libc-alpha/2016-05/msg00369.html
Commit 6c4798d3f08b81c2c52936b10e0fa872590c96ae "tools lib: Fix builds when glibc contains strlcpy()" reports to have fix fixed this bug. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6c4798d3f08b81c2c52936b10e0fa872590c96ae "Resolves: https://bugzilla.kernel.org/show_bug.cgi?id=118481" Why is this bug still openned?
(In reply to Mikhail Novosyolov from comment #2) > Commit 6c4798d3f08b81c2c52936b10e0fa872590c96ae "tools lib: Fix builds when > glibc contains strlcpy()" reports to have fix fixed this bug. > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ > ?id=6c4798d3f08b81c2c52936b10e0fa872590c96ae > > "Resolves: https://bugzilla.kernel.org/show_bug.cgi?id=118481" > > Why is this bug still openned? Because nobody asked to close, right?