public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@fedoraproject.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Laura Abbott <labbott@redhat.com>,
	Andy Lutomirski <luto@kernel.org>,
	"H . J . Lu" <hjl.tools@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	X86 ML <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Clifton <nickc@redhat.com>,
	Cary Coutant <ccoutant@gmail.com>
Subject: Re: [RFC PATCH 0/3] Salted build ids via linker sections
Date: Mon, 26 Mar 2018 11:58:55 +0200	[thread overview]
Message-ID: <20180326095855.GA9061@wildebeest.org> (raw)
In-Reply-To: <CAK7LNAQTf_tVvks==_wGsEeNs6Bpdcfy9k39fpzneFvVZGAOiA@mail.gmail.com>

Hi,

On Mon, Mar 26, 2018 at 04:48:11PM +0900, Masahiro Yamada wrote:
> 2018-03-21 10:46 GMT+09:00 Laura Abbott <labbott@redhat.com>:
> > In Fedora, the debug information is packaged separately (foo-debuginfo) and
> > can be installed separately. There's been a long standing issue where only one
> > version of a debuginfo info package can be installed at a time. Mark Wielaard
> > made an effort for Fedora 27 to allow parallel installation of debuginfo (see
> > https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo for
> > more details)
> 
> Is this a kernel-specific problem?
> 
> IIUC, the URL above is discussing packages in general.
> 
> Any executable from slightly different versions
> could result in identical ELF.
> If so, will you tweak link process of every package
> that needs parallel installation?

For almost any package it isn't necessary to tweak the link process
because the build-id can be tweaked if necessary at any stage of the
package process (the most convenient is during debuginfo splitting,
because the debuginfo contains almost all the information of the
build environment). The kernel vdso build is a bit special because it
embeds the executable also inside the kernel image (so it shows up at
runtime again not from the file system, but by being inserted into the
process by the kernel), where packaging tools cannot easily find it.

Cheers,

Mark

      reply	other threads:[~2018-03-26 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21  1:46 [RFC PATCH 0/3] Salted build ids via linker sections Laura Abbott
2018-03-21  1:46 ` [RFC PATCH 1/3] kbuild: Introduce build-salt generated header Laura Abbott
2018-03-21  1:46 ` [RFC PATCH 2/3] kbuild: Link with generated build-salt header Laura Abbott
2018-03-21  1:46 ` [RFC PATCH 3/3] x86/vdso: Add build salt to the vDSO Laura Abbott
2018-03-21  9:40 ` [RFC PATCH 0/3] Salted build ids via linker sections Nick Clifton
2018-03-26  7:48 ` Masahiro Yamada
2018-03-26  9:58   ` Mark Wielaard [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=20180326095855.GA9061@wildebeest.org \
    --to=mjw@fedoraproject.org \
    --cc=ccoutant@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=labbott@redhat.com \
    --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