Received: by 10.192.165.148 with SMTP id m20csp2732419imm; Sun, 6 May 2018 23:30:26 -0700 (PDT) X-Google-Smtp-Source: AB8JxZom0tCNS426lS86jOOq09Y9mybMee/ToWvFYLkOsJvVfGXdMDQOJLK+t0FM/oOuJnz8GxnV X-Received: by 2002:a17:902:7402:: with SMTP id g2-v6mr37822042pll.246.1525674626665; Sun, 06 May 2018 23:30:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525674626; cv=none; d=google.com; s=arc-20160816; b=kz9eDAtvOmVd73LE9LP74vzF0I9BP5VuanHH5KvBgyctwQKuAKzznEIsr3O5YqjThU wSWsKHMJ0W3ztXKg2OsxNtnAXPsqvztV9JqzdgGL2IuKwauxKmpqD2Veuht3XwZI1mvB Mv8w0jHRZy9XYze5MjwOBCyc395bKjHRJjMpLyD/nKxoMFa2VSjjvU9OLXnO6/yhKAOL piXqUT7PjSX15FHb4Rci60i/0z6SdWG8OyoZl/J0V0rsjMGRrfIPqq+R4Wymh0UhUjYE oUj8fMsKV74u9GEwtdST3XK4EDQ4LCClID8BCuhx+IpNa5CeTMDzNaZ7FylfrE1smclx Ytwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature:dkim-filter :arc-authentication-results; bh=Youx/S7XIS7YEOuhD7vp5BEhdkMrY1ngR1ymvFrfkTI=; b=xUViLgCHxDsdYCL5bQm3WgNpIBxZkFH87VsnHQV3hqKqlrLr4ro7Ju2ao1CvqiuRgl 7BlPTJRkt7bufalWVq0beVyZBLqUBdtN/2aVrUgkHpLrEx+NnMoe6CLgWPUw9QNc0vQI AvIv+TdrmdymUq39LGzyydIY+U67XR75/+gFaKWagHq1KALu9TFAAnSLyvPmTXDXLu40 2/h9GKSFRiIc07a7Gm4z6FrehkZNw2z1vc5iAPR9UeIcJkigENxag5goxUf9i/mj9bmC QK6QZEH7PfZLmr87gtrzMal2qCvQ4ubvj+XSYZVyf15tKOwTXN6oVVH7Zc4P5vZ8DscU agSQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=aCfg4VHJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p73si18779593pfk.275.2018.05.06.23.30.12; Sun, 06 May 2018 23:30:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=aCfg4VHJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751907AbeEGG34 (ORCPT + 99 others); Mon, 7 May 2018 02:29:56 -0400 Received: from conssluserg-05.nifty.com ([210.131.2.90]:35094 "EHLO conssluserg-05.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750884AbeEGG3w (ORCPT ); Mon, 7 May 2018 02:29:52 -0400 Received: from mail-vk0-f43.google.com (mail-vk0-f43.google.com [209.85.213.43]) (authenticated) by conssluserg-05.nifty.com with ESMTP id w476TUgp007443; Mon, 7 May 2018 15:29:31 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com w476TUgp007443 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1525674571; bh=Youx/S7XIS7YEOuhD7vp5BEhdkMrY1ngR1ymvFrfkTI=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=aCfg4VHJkr5nptDC5g8DW8oUyE5YiW8fNqBlIdbs+YRTdNgPs1Ga9MPTo+Q1Q+vJu selyUiZj9gBVqUszyrInOQssgJ8SgJSvMBnCDVX13ys+8HchFkNwAUriPYSSPjLjpl MW6Yp/wHHIgHQ8IPo2GItzVTxYh9kQu/l/woyxAMlzuBkfHr5TD2P0wBQFnFcyCq0q iwsN+o6VEFDARJ2enp6brPj0gHqXP1B71iMqfnIgx3oU10seFsgBu+qyPSF3WcRmjj YHDbQV5N5ZTYF48jhoI554lfjyvxy67jqbyPJOFrzwP9DZXr2eJfRGZdQx09ZdtNHF cZ9AfhtyVG65A== X-Nifty-SrcIP: [209.85.213.43] Received: by mail-vk0-f43.google.com with SMTP id m144-v6so16747285vke.4; Sun, 06 May 2018 23:29:31 -0700 (PDT) X-Gm-Message-State: ALQs6tBY7w0ra2Cvt3eG1vebw/yFq+FjaqdOOstiPGdwRp/VKiE4+kat iDcBF/BfidebNHfaBnlM1BYmIKr/L1zL8ZL77kM= X-Received: by 2002:a1f:2f8a:: with SMTP id v132-v6mr30492315vkv.34.1525674570039; Sun, 06 May 2018 23:29:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.85.216 with HTTP; Sun, 6 May 2018 23:28:49 -0700 (PDT) In-Reply-To: <20180329180112.11055-1-labbott@redhat.com> References: <20180329180112.11055-1-labbott@redhat.com> From: Masahiro Yamada Date: Mon, 7 May 2018 15:28:49 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFCv2 PATCH 0/3] Salted build ids via linker sections To: Laura Abbott Cc: Andy Lutomirski , mjw@fedoraproject.org, "H . J . Lu" , Linus Torvalds , X86 ML , Linux Kernel Mailing List , Nick Clifton , Cary Coutant , Linux Kbuild mailing list Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2018-03-30 3:01 GMT+09:00 Laura Abbott : > Hi, > > This is v2 of my proposal to allow unique build-ids in the kernel. from > last time: > > "" > 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) > > Part of the requirement to allow this to work is that build ids are > unique between builds. The existing upstream rpm implementation ensures > this by re-calculating the build-id using the version and release as a > seed. This doesn't work 100% for the kernel because of the vDSO which is > its own binary and doesn't get updated. After poking holes in a few of my > ideas, there was a discussion with some people from the binutils team about > adding --build-id-salt to let ld do the calculation debugedit is doing. There > was a counter proposal made about adding some extra information via a .comment > which will affect the build id calculation but just get stripped out. > "" I think you already know '--build-id=uuid' linker option. Doesn't this solve your problem? The disadvantage of this option is, we will lose reproducible building because --build-id=uuid adds every time random salt. The advantage is, the implementation is even simpler, and easier to migrate to --build-id-salt once it is supported in the future. > This v2 cleans up the naming to be consistent and also switches to a > config option vs. an environment variable. I've seen some sporadic > failures about missing the generated header so I think I'm still missing > a dependency somewhere. Right. There is no dependency between 'prepare' and 'scripts' in the top Makefile. Therefore, Kbuild can run them simultaneously, which would cause a race in parallel building. 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. > > Thanks, > Laura > > > Laura Abbott (3): > kbuild: Introduce build-salt generated header > kbuild: Link with generated build-salt header > x86/vdso: Add build salt to the vDSO > > Makefile | 13 +++++++++++-- > arch/x86/entry/vdso/vdso-layout.lds.S | 3 +++ > init/Kconfig | 8 ++++++++ > scripts/.gitignore | 1 + > scripts/Makefile | 2 +- > scripts/build-salt.lds.S | 5 +++++ > scripts/gensalt | 21 +++++++++++++++++++++ > scripts/link-vmlinux.sh | 3 ++- > 8 files changed, 52 insertions(+), 4 deletions(-) > create mode 100644 scripts/build-salt.lds.S > create mode 100755 scripts/gensalt > > -- > 2.16.2 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Regards Masahiro Yamada