All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Bastian Blank <waldi@debian.org>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: Add build salt to the vDSO
Date: Mon, 29 Jun 2026 19:12:39 +0200	[thread overview]
Message-ID: <akKnh5c2IIJRAg23@alpha.franken.de> (raw)
In-Reply-To: <ajQY5adFB_yOfIl5@steamhammer.waldi.eu.org>

On Thu, Jun 18, 2026 at 06:12:21PM +0200, Bastian Blank wrote:
> The vDSO needs to have a unique build id in a similar manner
> to the kernel and modules. Use the build salt macro.
> 
> Signed-off-by: Bastian Blank <waldi@debian.org>
> ---
> I was not able to properly test this change, due to unavailable
> toolchain.
> 
>  arch/mips/vdso/elf.S | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/arch/mips/vdso/elf.S b/arch/mips/vdso/elf.S
> index a25cb147f1ca..821fcffe7655 100644
> --- a/arch/mips/vdso/elf.S
> +++ b/arch/mips/vdso/elf.S
> @@ -8,6 +8,7 @@
>  
>  #include <asm/isa-rev.h>
>  
> +#include <linux/build-salt.h>
>  #include <linux/elfnote.h>
>  #include <linux/version.h>
>  
> @@ -15,6 +16,8 @@ ELFNOTE_START(Linux, 0, "a")
>  	.long LINUX_VERSION_CODE
>  ELFNOTE_END
>  
> +BUILD_SALT
> +
>  /*
>   * The .MIPS.abiflags section must be defined with the FP ABI flags set
>   * to 'any' to be able to link with both old and new libraries.
> -- 
> 2.53.0

applied to mips-fixes

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2026-06-29 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 16:12 [PATCH] mips: Add build salt to the vDSO Bastian Blank
2026-06-29 17:12 ` Thomas Bogendoerfer [this message]

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=akKnh5c2IIJRAg23@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=waldi@debian.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.