linux-kernel - Re: 2.6.28-rc3-git1: spitz still won't boot

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]

Message-Id: <1226155540.5379.5.camel@dax.rpnet.com>
Date:	Sat, 08 Nov 2008 14:45:40 +0000
From:	Richard Purdie <rpurdie@...ys.net>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	Dmitry <dbaryshkov@...il.com>, Pavel Machek <pavel@...e.cz>,
	Eric Miao <eric.y.miao@...il.com>, Cyril Hrubis <metan@....cz>,
	lenz@...wisc.edu, kernel list <linux-kernel@...r.kernel.org>,
	Dirk@...er-online.de, arminlitzel@....de, pavel.urban@...cz,
	thommycheck@...il.com
Subject: Re: 2.6.28-rc3-git1: spitz still won't boot

On Fri, 2008-11-07 at 18:23 +0000, Russell King wrote:
> On Fri, Nov 07, 2008 at 05:57:33PM +0300, Dmitry wrote:
> > 2008/11/7 Pavel Machek <pavel@...e.cz>:
> > > On Fri 2008-11-07 21:23:41, Eric Miao wrote:
> > >> Well, IIRC spitz still needs the patch to change the vmlinux.ld.S.
> > >> Did you guys ever try that?
> > >
> > > I never heard about that patch, do you have it handy?
> > 
> > http://rpsys.net/openzaurus/patches/archive/pxa-linking-bug.patch
> > 
> > I plan to submit a bit modified version of this patch later.
> 
> That doesn't look like something that should be accepted.  Take a moment
> to put some thought into the question.  Why should we _allocate_ and
> contain the stack in the resulting image?  Does the stack contain any
> data that must be pre-initialized?
> 
> Obviously not.

Firstly, I don't think that patch should ever make it into a mainline
kernel. I can perhaps give some clues why its required though. I think
the bootloader on the zaurus truncates the image when writing the kernel
into flash using the standard flashing process. By having that much
extra padding on the end of the kernel, nothing important is lost.

How did the original 2.4 kernels ever work? Binutils used to be buggy
and left this padding in. Nobody therefore ever noticed the bug in the
bootloader.

The above theory is guesswork based on the kernels I've seen work and
not work and I wrote the patch mentioned above as a workaround a long
time ago and more pressing issues meant I never got back to it. I'd love
to see someone work out the problem for sure!

Cheers,

Richard

--
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/