mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Sverdlin <alexander.sverdlin@nokia.com>
To: Matija Glavinic Pecotic <matija.glavinic-pecotic.ext@nokia.com>,
	linux-mips@vger.kernel.org,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Nemanja Rakovic <nemanja.rakovic@syrmia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mips: vdso: Allow passing build path options
Date: Wed, 8 Jun 2022 11:11:31 +0200	[thread overview]
Message-ID: <b9634f95-bb88-d5a7-633b-b7082504549d@nokia.com> (raw)
In-Reply-To: <23e2afda-630a-f6fc-e211-a464b29496f4@nokia.com>

Hello Matija, Thomas,

On 04/04/2022 10:36, Matija Glavinic Pecotic wrote:
> vdso image is not reproducible in different build directories as build
> path defines vdso image contents via .notes, build ID. Build ID is
> hashed across all sections (prior stripping), debug sections included.
> With debug sections containing build paths, hash is impacted. Finally
> vmlinux is not reproducible as it will differ in vdso_data.
> 
> For users wanting reproducible builds, irrespective of build path, it
> is unwanted behavior. Issue is sorted out by passing related options
> via KAFLAGS, KCFLAGS, however due to mips' picking out specific/subset
> options, these are not getting passed through.
> 
> Allow related option to be taken if user specified them.
> 
> Signed-off-by: Matija Glavinic Pecotic <matija.glavinic-pecotic.ext@nokia.com>

Reviewed-by: Alexander Sverdlin <alexander.sverdlin@nokia.com>

> ---
>  arch/mips/vdso/Makefile | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/mips/vdso/Makefile b/arch/mips/vdso/Makefile
> index f72658b3a53f..b8296ef2bfcf 100644
> --- a/arch/mips/vdso/Makefile
> +++ b/arch/mips/vdso/Makefile
> @@ -35,8 +35,12 @@ cflags-vdso := $(ccflags-vdso) \
>  	-O3 -g -fPIC -fno-strict-aliasing -fno-common -fno-builtin -G 0 \
>  	-mrelax-pic-calls $(call cc-option, -mexplicit-relocs) \
>  	-fno-stack-protector -fno-jump-tables -DDISABLE_BRANCH_PROFILING \
> -	$(call cc-option, -fno-asynchronous-unwind-tables)
> +	$(call cc-option, -fno-asynchronous-unwind-tables) \
> +	$(filter -ffile-prefix-map%,$(KBUILD_CFLAGS)) \
> +	$(filter -fmacro-prefix-map%,$(KBUILD_CFLAGS)) \
> +	$(filter -fdebug-prefix-map%,$(KBUILD_CFLAGS))
>  aflags-vdso := $(ccflags-vdso) \
> +	$(filter --debug-prefix-map%,$(KBUILD_AFLAGS)) \
>  	-D__ASSEMBLY__ -Wa,-gdwarf-2
>  
>  ifneq ($(c-gettimeofday-y),)

-- 
Best regards,
Alexander Sverdlin.

           reply	other threads:[~2022-06-08  9:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <23e2afda-630a-f6fc-e211-a464b29496f4@nokia.com>]

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=b9634f95-bb88-d5a7-633b-b7082504549d@nokia.com \
    --to=alexander.sverdlin@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=matija.glavinic-pecotic.ext@nokia.com \
    --cc=nemanja.rakovic@syrmia.com \
    --cc=tsbogend@alpha.franken.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®