Hello, tried to look if this issue could be closed. Unfortunately can also not reproduce it in a Debian Jessie i386 VM with 21.0-1 from snapshot.debian.org.
Following the mail from message #20 [1], it leads to a bug in [2] which points in the attachement to the function read_klog. Upstream got a patch in that function in [3] that points to "bnc #870383". This could possibly be bugzilla.novell.com [4] to which I unfortunately have no access. Running 21.0-1 with valgrind points also to that function. > floppy.1: get nvram==1368== Source and destination overlap in > strcpy(0x4b95ab3, 0x4b95ac2) ==1368== at 0x402D536: strcpy (vg_replace_strmem.c:458) ==1368== by 0x4071DD1: read_klog (in /usr/lib/i386-linux-gnu/libhd.so.21.0) ==1368== by 0x405602F: hd_scan_floppy (in /usr/lib/i386-linux-gnu/libhd.so.21.0) ==1368== by 0x40602CE: hd_scan (in /usr/lib/i386-linux-gnu/libhd.so.21.0) ==1368== by 0x4060F2C: hd_list (in /usr/lib/i386-linux-gnu/libhd.so.21.0) ==1368== by 0x804C113: ??? (in /usr/sbin/hwinfo) ==1368== by 0x804A00D: ??? (in /usr/sbin/hwinfo) ==1368== by 0x4249A62: (below main) (libc-start.c:287) Both 21.3-1 and 21.6-1 do not show such a warning with valgrind. Unfortunately 21.3-1 has already the change from [4] included but is in message #15 said to still show a stack smashing. [1] http://lists.opensuse.org/opensuse-factory/2012-08/msg00099.html [2] https://bugzilla.opensuse.org/show_bug.cgi?id=774430 [3] https://github.com/openSUSE/hwinfo/commit/52c8ece11cfa88fa9eca2bf4ed9be844a8077840#diff-2e22318ded9983bf2a7311062a58f18c [4] https://bugzilla.novell.com/show_bug.cgi?id=870383 Kind regards, Bernhard
