lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 8 Feb 2008 17:14:50 +0100
From:	"Abel Bernabeu" <abelbg@...rp.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Elf loader crash while zero-filling .bss

2008/1/31, Abel Bernabeu <abelbg@...rp.com>:
> 2008/1/30, Abel Bernabeu <abelbg@...rp.com>:
>
> > Now I am trying to execute some bigger C applications: in instance
> > BusyBox. I've chosen the buildroot package in order to produce a small
> > "distro".
> >
> > Then I've tried to boot the system using init=/bin/sh but I am getting
> > a crash while loading this non-toy binary.

Hi guys,

Excuse me for posting even another message about the same crash (I am
responding myself anyway :). It is my crash and I will find why
happens! :D

I've found THE COMMON DENOMINATOR present in all the binaries that get
my kernel crash.

The offset of some sections fall in the middle of the .bss section. In
instance, look at the sections 12 (.comment) and 13 (.ARM.atributes).
Both sections are overlapping with 11 (.bss):

[11] .bss                 NOBITS       0001143c 00143c 000048  0 WA     0   0  4
[12] .comment             PROGBITS     00000000 00143c 000094  0        0   0  1
[13] .ARM.attributes      SHT_LOPROC+3 00000000 0014d0 000010  0        0   0  1
[14] .shstrtab            STRTAB       00000000 0014e0 00007b  0        0   0  1
[15] .symtab              SYMTAB       00000000 001804 000c70 16       16  92  4
[16] .strtab              STRTAB       00000000 002474 000840  0        0   0  1

Is this fact meaningful??

I don't think this .elf file is correct and you can blame my
cross-compiler building skills... but the kernel should be friendly
enough to tell me about the problem instead of crashing :)

Any ideas?

Yours, Abel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ