[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#679377: Segmentation fault when initramfs is booting

tags 679377 + moreinfo

On 28.06.2012 13:14, Jordi Pujol wrote:
> Package: busybox
> Version: 1:1.20.0-4
> Severity: important
> the patch "shell-ash-export-HOME.patch" causes a segmentation fault when 
> initramfs boots,
> I believe that this fault occurs the first time that initramfs looks for some 
> executable in the initramfs filesystem,

Does whole thing actually work?  Why do you think it is this patch
which causes the SIGSEGV?  The change in this patch is quite, well,
innocent, it does not look like it can be a cause for any such issues.

Can you describe your initramfs/environment a bit?  Maybe give me
access to your initramfs for testing?

> Also, the latest release of busybox, 1.20.1 is a bit different of that, and 

Different of what, exactly?  The version of busybox you're
filing bugreport against is actually 1.20.1, so there are
two questions actually: what is different, and different
between what and what? -- since you're comparing the same
thing with itself.

> more upstream stable patches have been added. A new release can be packaged 
> containing this changes,

The only upstream change not included in debian package is
busybox-1.20.1-mke2fs.patch, which is only relevant for
busybox-static since other variants don't enable mkfs.

> Modifying this, busybox works fine,
> http://livenet.selfip.com/ftp/debian/package-
> modifications/busybox_1.20.1-1.lnet1.debian.tar.gz

Now that's fantastic.  Let's see.

diff -u -p -r debian/patches/series lnet/patches/series
--- 1.20.0-4/patches/series	2012-06-12 22:04:46.000000000 +0400
+++ lnet1/patches/series	2012-06-22 19:15:34.000000000 +0400
@@ -1,6 +1,4 @@
 # we need to get rid of this one:
@@ -11,10 +9,12 @@ u-mount-FreeBSD-support.patch

 # FTBFS on non-linux

 # upstream stable patches

So you reverted all fixes which went into 1.20.1 bugfix
release, you reverted my ps-get-uptime.patch but added
busybox-1.20.1-ps.patch (it has exactly the same content),
added busybox-1.20.1-mke2fs.patch (which is not relevant
for the issue in question), and reverted shell-ash-export-HOME.patch
which looks completely innocent here, without trying to
understand what it does and WHY it is here.

Wherer's the improvement?  This is definitely NOT a way
to do things.

So, I really want to know more about your environment and
the segfault.  I don't see any segfaults here.



Reply to: