Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp3010745imm; Thu, 17 May 2018 01:39:05 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpKcpAwhJtig1wzj6KXt9hSt0sdfXL/gy8EuQ1KQakj+fKUNAB4Pa0a44iArIv22Nl2fsmF X-Received: by 2002:a62:dc4e:: with SMTP id t75-v6mr4313642pfg.139.1526546345732; Thu, 17 May 2018 01:39:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526546345; cv=none; d=google.com; s=arc-20160816; b=0ZMHIvQeM8wasKtYZ9q3L8kweN13KDHXkA1Hu4GntQUEVumBH3oZwVdMTP3/qD+Kcf dMOcDu70lrDy/zMd0A4Gjpdxyjj+lKK2pLcKLUZNP29S5tzhxXSRX7CRaexoLG1XOmxK NdeyaeGdALQ6AtU9K9CltnhydIqM5xP5Vlc51kTM8nuaAcNro8MtCGsHPnQp/Ij68R7y 5ND7clehHJihDNtEqbUZVR1TsLb0vy6Pi2ERAOe2s1QR2Qs8+MMlXW0G7XzS91ElZuZN Ga0SRPx/vZ7NCsoMBXHHfzOnbFiiLQ8VAt5aZQvlxeGEu4HaqB2mRhY0T4a7DjXJWrU2 QXuQ== 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=J8UV62807LDY1rBZ7UaLRWH0peyCQ0HgYGTMJvZMMas=; b=N71tbTwDrZlXaFy+QK3pUSurS+5nq3Yytkko4AIFW3Q4UZ15D8EDurDobVPU7scNBC 3YeYCyX8RgKL5G6GGgX+CMUQu3JQBJggkMyeaPbj0+ML3UtGfI4aP9e6KKszHO7HV7i6 sddHN40+nW1G11G9JuAvPjsg8I2g40GPZX9zq893ZrsxjF3cAnzhcGe0VgEirXf//VH8 gEhTXaksAsXTcFChCVy/vjEUIvouB4CUHp8EKynfxiOqRWkHeFH0VY/hVBvpOjAlBS6r Pl/0vKcT/ou2gNkXmm+ofh1S1tLfTwm0Zcav+KvHNEqu2gJaHzgxkvjOq9Ynm9WaqJUE kLGA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=YGabiTDI; 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 h193-v6si3748966pgc.57.2018.05.17.01.38.51; Thu, 17 May 2018 01:39:05 -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=YGabiTDI; 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 S1751914AbeEQIii (ORCPT + 99 others); Thu, 17 May 2018 04:38:38 -0400 Received: from conssluserg-05.nifty.com ([210.131.2.90]:51916 "EHLO conssluserg-05.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750924AbeEQIif (ORCPT ); Thu, 17 May 2018 04:38:35 -0400 Received: from mail-vk0-f47.google.com (mail-vk0-f47.google.com [209.85.213.47]) (authenticated) by conssluserg-05.nifty.com with ESMTP id w4H8cKHT016871; Thu, 17 May 2018 17:38:21 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com w4H8cKHT016871 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1526546301; bh=J8UV62807LDY1rBZ7UaLRWH0peyCQ0HgYGTMJvZMMas=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=YGabiTDIFEMcg9nDiWGOpQz/XnDyASv2LeaZU6YYuVEEbSC6DYhkkxX8HV2E2yvGj ZgCvXqxTJJe/UmeA7o4KZ8oVh1GN7HJsk1PQ/QvRQGtVptmjEYSLKqcGyBSHhFZYx/ mFx0CL52BThLG/HFL4hIhW4wK0QMdV/vC3ZDRe4IAsQ1Relm4LqdHBlI3Ps/isFXH6 p9QhsCxL2MsVaHAeq5yFGwSRtFNWlbEVrvaNZ++W045uct8iuZFXInEMktSaj9iMY5 nLDvCUv/IhK6FHMbAnWNOP3Y0TglplpxPtPwWIRaF4ijg8+0vIxJ+q0k+ru306GzA3 +P9v3maiCG9Pw== X-Nifty-SrcIP: [209.85.213.47] Received: by mail-vk0-f47.google.com with SMTP id x191-v6so2196161vke.10; Thu, 17 May 2018 01:38:21 -0700 (PDT) X-Gm-Message-State: ALKqPweMZqj3DRHALLAgJlK7sWans5E0REmFnZUSF6xSW54gjXjEmvur 49sEkjkwvF6ebboGOC9TZBOlz+zmsA+be4NY8XE= X-Received: by 2002:a1f:acc4:: with SMTP id v187-v6mr3418092vke.11.1526546300389; Thu, 17 May 2018 01:38:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.85.216 with HTTP; Thu, 17 May 2018 01:37:40 -0700 (PDT) In-Reply-To: References: <20180329180112.11055-1-labbott@redhat.com> From: Masahiro Yamada Date: Thu, 17 May 2018 17:37:40 +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 , Mark Wielaard , "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-05-15 6:02 GMT+09:00 Laura Abbott : > On 05/06/2018 11:28 PM, Masahiro Yamada wrote: >> >> 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. >> >> > > It could, theoretically. The reproducibility is nice though and > I'd like to keep the kernel close to matching what other packages > do though. Okay. I left some comments in v2 about improvement, and cause of the sporadic build failures. Will wait for v3. -- Best Regards Masahiro Yamada