Tiny Core Linux

Tiny Core Base => TCB Bugs => Topic started by: ali on August 30, 2011, 12:17:35 AM

Title: bootcode segmentation fault 3.8.3
Post by: ali on August 30, 2011, 12:17:35 AM

Hello,
Let me get straight to the point.
This is my grub entry

Code: [Select]

menuentry "Tinycore" {
linux /boot/bzImage quiet tce=sda8 user=ali laptop tz=GMT+2 host=mini
initrd /boot/microcore.gz
}
when it boots it says

Code: [Select]

Adding user ali
Password for ali has changed
Segmentation faultI think there may be something wrong with the user bootcode

Title: Re: bootcode segmentation fault 3.8.3
Post by: maro on August 30, 2011, 01:30:46 AM

OK, I believe to have been able to reproduce the reported issue and identified the likely "culprit":

Code: [Select]

ali@mini:~$ dmesg | grep segfault
chpasswd[201]: segfault at 8000000 ip b76a1839 sp bfaebecc error 4 in libc-2.11.1.so[b7632000+13d000]which is most likely a consequence of line 17 in '/etc/init.d/tc-config': echo "$USER":tcuser | /usr/sbin/chpasswd -m

As the same could be found in MC 3.8.2 (but not in MC 3.8.1) I'm pretty sure that means a regression in BusyBox v1.19.0 for the 'chpasswd' applet.

To which degree this segmentation fault is having a negative impact is something I can't tell for sure. At least as the "Password for 'ali' changed" message appears and '/etc/shadow' has indeed been updated I suspect the fault stems from the few "cleanup" statements following in the source code after that message has been printed. So I personally would not worry too much, but there is always the option to fall back to MC 3.8.1 (or earlier) where an older versions of BusyBox was used.

Title: Re: bootcode segmentation fault 3.8.3
Post by: roberts on August 30, 2011, 02:15:13 AM

Confirmed busybox chpasswd applet is the culprit.

Title: Re: bootcode segmentation fault 3.8.3
Post by: maro on August 30, 2011, 04:37:58 AM

I've now raised a bug report (https://bugs.busybox.net/show_bug.cgi?id=4105) against BusyBox about it.

Title: Re: bootcode segmentation fault 3.8.3
Post by: maro on September 11, 2011, 07:06:15 PM

Apparently the bug has now been fixed with this commit (http://git.busybox.net/busybox/commit/?id=d2fe2ba08dd84cd7e94d1ae3e2e9c12ca2b4d561). I guess instead of using a (potentially) "leaky" patch (http://distro.ibiblio.org/tinycorelinux/3.x/release/src/busybox-1.19.0_chpasswd.patch) it might be prudent to give the "official solution" a go (which is obviously expected to appear in BusyBox v1.19.3).