From: Mark Wielaard <mjw@fedoraproject.org>
To: Laura Abbott <labbott@redhat.com>,
Andy Lutomirski <luto@kernel.org>,
"H . J . Lu" <hjl.tools@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
X86 ML <x86@kernel.org>,
linux-kernel@vger.kernel.org, Nick Clifton <nickc@redhat.com>,
Cary Coutant <ccoutant@gmail.com>,
linux-kbuild@vger.kernel.org
Subject: Re: [RFCv2 PATCH 0/3] Salted build ids via linker sections
Date: Fri, 30 Mar 2018 14:40:19 +0200 [thread overview]
Message-ID: <1522413619.15770.88.camel@fedoraproject.org> (raw)
In-Reply-To: <20180329180112.11055-1-labbott@redhat.com>
On Thu, 2018-03-29 at 11:01 -0700, Laura Abbott wrote:
> I'm still mostly looking for feedback whether
> this would be acceptable for merging or if we should just persue a
> --build-id-salt in binutils.
Personally I would go with this approach. It seems simple and it might
take years before a new linker option is available everywhere.
To simplify things I think you could just always add the extra vdso
.comment initialized to something like KERNELRELEASE. Which distros
seem to update anyway to include their build number, so they wouldn't
need to do anything special to "update the build salt".
Cheers,
Mark
next prev parent reply other threads:[~2018-03-30 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 18:01 [RFCv2 PATCH 0/3] Salted build ids via linker sections Laura Abbott
2018-03-29 18:01 ` [RFCv2 PATCH 1/3] kbuild: Introduce build-salt generated header Laura Abbott
2018-03-29 18:01 ` [RFCv2 PATCH 2/3] kbuild: Link with generated build-salt header Laura Abbott
2018-05-07 6:38 ` Masahiro Yamada
2018-03-29 18:01 ` [RFCv2 PATCH 3/3] x86/vdso: Add build salt to the vDSO Laura Abbott
2018-05-07 6:42 ` Masahiro Yamada
2018-03-30 12:40 ` Mark Wielaard [this message]
2018-05-07 6:58 ` [RFCv2 PATCH 0/3] Salted build ids via linker sections Masahiro Yamada
2018-05-08 2:49 ` Andy Lutomirski
2018-05-14 20:51 ` Laura Abbott
2018-05-07 6:28 ` Masahiro Yamada
2018-05-14 21:02 ` Laura Abbott
2018-05-17 8:37 ` Masahiro Yamada
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=1522413619.15770.88.camel@fedoraproject.org \
--to=mjw@fedoraproject.org \
--cc=ccoutant@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=labbott@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=nickc@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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