mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Jan Beulich" <JBeulich@suse.com>
Cc: <mingo@elte.hu>, <tglx@linutronix.de>, <hpa@zytor.com>,
	"Andy Lutomirski" <luto@amacapital.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86-64: fix vDSO build
Date: Wed, 9 Jul 2014 16:30:15 -0700	[thread overview]
Message-ID: <20140709163015.96c76a7b0e84632bc006fda0@linux-foundation.org> (raw)
In-Reply-To: <53B5861E02000078000204D1@mail.emea.novell.com>

On Thu, 03 Jul 2014 15:34:38 +0100 "Jan Beulich" <JBeulich@suse.com> wrote:

> Certain ld versions (observed with 2.20.0) put an empty .rela.dyn
> section into shared object files, breaking the assumption on the number
> of sections to be copied to the final output. Simply discard any empty
> SHT_REL and SHT_RELA sections to address this.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Cc: Andy Lutomirski <luto@amacapital.net>
> ---
>  arch/x86/vdso/vdso2c.h |    3 +++
>  1 file changed, 3 insertions(+)
> 
> --- 3.16-rc3/arch/x86/vdso/vdso2c.h
> +++ 3.16-rc3-x86-vdso-build/arch/x86/vdso/vdso2c.h
> @@ -93,6 +93,9 @@ static void BITSFUNC(copy_section)(struc
>  	uint64_t flags = GET_LE(&in->sh_flags);
>  
>  	bool copy = flags & SHF_ALLOC &&
> +		(GET_LE(&in->sh_size) ||
> +		 (GET_LE(&in->sh_type) != SHT_RELA &&
> +		  GET_LE(&in->sh_type) != SHT_REL)) &&
>  		strcmp(name, ".altinstructions") &&
>  		strcmp(name, ".altinstr_replacement");

Tested-by: Andrew Morton <akpm@linux-foundation.org>

(hint)

  parent reply	other threads:[~2014-07-09 23:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 14:34 Jan Beulich
2014-07-03 15:33 ` Andy Lutomirski
2014-07-03 23:09 ` Boris Ostrovsky
2014-07-09 23:30 ` Andrew Morton [this message]
2014-07-10 23:04 ` [tip:x86/urgent] x86-64, vdso: Fix vDSO build breakage due to empty .rela.dyn tip-bot for Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140709163015.96c76a7b0e84632bc006fda0@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=JBeulich@suse.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®