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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0910010905340.5982@dr-wily.mit.edu>
Date:	Mon, 12 Oct 2009 10:47:41 -0400 (EDT)
From:	Tim Abbott <tabbott@...lice.com>
To:	Greg Ungerer <gerg@...pgear.com>
cc:	Greg Ungerer <gerg@...inux.org>, linux-kernel@...r.kernel.org,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: [PATCH v2 2/2] m68knommu: Clean up linker script using new linker
 script macros.

On Thu, 1 Oct 2009, Greg Ungerer wrote:

> Hi Tim,
> 
> Tim Abbott wrote:
> > Signed-off-by: Tim Abbott <tabbott@...lice.com>
> > Cc: Greg Ungerer <gerg@...inux.org>
> 
> This results in kernels that don't boot for me. I haven't done
> any more debugging than to just try booting at this time.
[...]
> 
> Does that look like what you would have expected?

Basically.  I'm a bit surprised that the .init_begin section doesn't show 
up, but I'm pretty sure that this is because .init_begin would have had 
size zero as the previous section's end was already page-aligned.

> I suspect the problem may lie in the binary conversion of this
> elf file to a raw binary for booting. This uses objcopy with
> "-O binary". The resulting binary files are different in size
> with and without the patch by about 2582 bytes. Suspicious
> me thinks.

I don't any good ideas for what in patch is likely to be responsible.  
Would it be helpful to debug if I split this into ~5 very small patches so 
that we can find out what part of the patch is responsible?

	-Tim Abbott
--
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