linux-kernel - Re: [PATCH] ia64 vDSO vs --build-id

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] [day] [month] [year] [list]

Date:	Thu, 25 Oct 2007 12:08:12 -0400
From:	Doug Chapman <dchapman@...hat.com>
To:	Roland McGrath <roland@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org,
	tony.luck@...el.com
Subject: Re: [PATCH] ia64 vDSO vs --build-id

On Thu, 2007-10-18 at 15:11 -0700, Roland McGrath wrote:
> When gcc uses --build-id by default, the gate.lds.S linker script runs afoul
> of the new note section and produces a bad DSO image.  This fixes it.
> 
> Signed-off-by: Roland McGrath <roland@...hat.com>
> 
> --- a/arch/ia64/kernel/gate.lds.S
> +++ b/arch/ia64/kernel/gate.lds.S
> @@ -20,6 +20,8 @@ SECTIONS
>  	.gnu.version_d		: { *(.gnu.version_d) }
>  	.gnu.version_r		: { *(.gnu.version_r) }
>  
> +	.note			: { *(.note*) }		:readable	:note
> +
>  	.dynamic		: { *(.dynamic) }	:readable	:dynamic
>  
>  	/*
> @@ -83,6 +85,7 @@ PHDRS
>  	epc		PT_LOAD	FILEHDR PHDRS	FLAGS(1);	/* PF_X */
>  #endif
>  	dynamic		PT_DYNAMIC		FLAGS(4);	/* PF_R */
> +	note		PT_NOTE			FLAGS(4);	/* PF_R */
>  	unwind		PT_IA_64_UNWIND;
>  }
>  
> -

Any news on this?  It does not appear to have been commited to git.
This issue is blocking our bringup of Fedora on ia64.  The Fedora gcc
uses the --build-id option by default leading to a hang during bootup
without this patch.

thanks,

- Doug


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