linux-kernel - Re: [PATCH 22/30] microblaze_mmu_v1: Update linker script for MMU

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]

Date:	Wed, 29 Apr 2009 13:27:49 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	monstr@...str.eu
Cc:	linux-kernel@...r.kernel.org, john.williams@...alogix.com
Subject: Re: [PATCH 22/30] microblaze_mmu_v1: Update linker script for MMU

On Monday 27 April 2009, monstr@...str.eu wrote:
> --- a/arch/microblaze/kernel/vmlinux.lds.S
> +++ b/arch/microblaze/kernel/vmlinux.lds.S
> @@ -17,8 +17,11 @@ ENTRY(_start)
>  jiffies = jiffies_64 + 4;
>  
>  SECTIONS {
> +#ifdef CONFIG_MMU
> +       . = CONFIG_KERNEL_START;
> +#else
>         . = CONFIG_KERNEL_BASE_ADDR;
> -
> +#endif
>         .text : {
>                 _text = . ;
>                 _stext = . ;

This change looks a bit bogus, can't you use the same symbol for
both? I guess either one would be fine, but I don't see a reason
for them to be different.

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