Received: by 10.192.165.148 with SMTP id m20csp2753073imm; Mon, 7 May 2018 00:00:26 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoqd80A+D7RqaXGCionQXst3nVr8Miszuh7VaS+yXihYhORC0DV0M4SJPu2hte4mOZPHlx7 X-Received: by 2002:a65:6603:: with SMTP id w3-v6mr29412798pgv.151.1525676426628; Mon, 07 May 2018 00:00:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525676426; cv=none; d=google.com; s=arc-20160816; b=NbLtQktEEBJvJK+giDao2+3SAPaX5XI91IG8dCneWnxfI9jbInJhUUq0JNmSYEKlOw R64tPKiZa40zqePCFW9BXPIcpVBhP+c7XoL6U01p6PvKtA0ideLizOBWM9I7uPQRiz9L AjtKCP8ySNS0k47OgqoOq/6uVgdIX2fOwihOsp7sPZ4jNg4e0UX8UI+l40A5isI3zh6B XzRUlwvbxcOco2I1AQ09bL6nSUW7NlUFtG/U57DHISOocaWl1QHFNabBAS/u/vCxfux3 sdT8Ylbdp5OFfBJCSGRXEHdeysPLXjYwcWD4RO1IWv8Pch+rVFWTAz/p3HBqXA6pJh9a isjg== 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=ARuzSeItM0QKhTQ57Qkq9xV/3Sh1wJxLEf/Sc3kdNLU=; b=Mu+ekl3whZ5+9MxHDTOIvCPnlx7Crmk45u1cVMhS098mbMb+WQJvYYZwVwHPH3T1aJ b9DQNzwsaBLiKGdx2Cu1Oid3vvkCCJvHDtQJnu7DE55G+n7+fzlf92in6BgjbIhx3Cn4 dLjW3GeZEAqOuQslWSQmzqOB6O5WPLGmGLQwsWQdUj/Omr6SaFvkQvsYNDQTVVXSB/HV hkmlTLKYq0Bh0ZqioF64POcukF5f/xaj+S7lrvnlRQ9E0OpHW7cBwiUZ+PTQV4YpUI78 5hr6tnQAtm7oueZru0Z/1C2aCuuRXFt8BEz6p1LnU7QgDjS5jkefIURH/ycNCDvf0UpD xs1w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=t/4C5chZ; 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 5si19144996pfd.73.2018.05.07.00.00.12; Mon, 07 May 2018 00:00: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=t/4C5chZ; 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 S1751903AbeEGG7v (ORCPT + 99 others); Mon, 7 May 2018 02:59:51 -0400 Received: from conssluserg-01.nifty.com ([210.131.2.80]:62854 "EHLO conssluserg-01.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750795AbeEGG7s (ORCPT ); Mon, 7 May 2018 02:59:48 -0400 Received: from mail-ua0-f169.google.com (mail-ua0-f169.google.com [209.85.217.169]) (authenticated) by conssluserg-01.nifty.com with ESMTP id w476xc8j027910; Mon, 7 May 2018 15:59:38 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com w476xc8j027910 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1525676379; bh=ARuzSeItM0QKhTQ57Qkq9xV/3Sh1wJxLEf/Sc3kdNLU=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=t/4C5chZ0CM/xkUqL2kSdhCvp4QueHhHekqGP7X2WdbRpzUQr8vuPPfWH1eDA5Dg/ 0QsT/zUr04Nn5YgrjArzBy7OOQ6vjKu7PHTlNFIYFri1FHgva4SlBz7gfpmwrCvkSx t016BRhkGrdicsblQ5pecKw5bKxvdNngxaCz+d+cJuzDwqm7F5TxwqYktwOeyqsW25 991BBzysq/BFZ8NjuC2Mua7MkbWD8/qzmO0Myk9PJLcO1xvd6XInKGoOVZ44laH0x1 IJ+wU2ZAU5lukuQc0matYQ/JyKQ2L+VDgEHdA3ReylUtEFjHFa4CCxZ+36WCkZi9Sa kBTN0vOLlvevQ== X-Nifty-SrcIP: [209.85.217.169] Received: by mail-ua0-f169.google.com with SMTP id i2so17728425uah.0; Sun, 06 May 2018 23:59:38 -0700 (PDT) X-Gm-Message-State: ALQs6tB8Xe5QqSS6tMgFr+MRAZ/1ucPaT9oGO9LKrtjUXHbgTkGgxNy0 mYjQ+FHOkEvWnrtu4cecGimatHcK+lZhWJ1sG6c= X-Received: by 10.176.16.20 with SMTP id f20mr30666566uab.141.1525676377829; Sun, 06 May 2018 23:59:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.85.216 with HTTP; Sun, 6 May 2018 23:58:57 -0700 (PDT) In-Reply-To: <1522413619.15770.88.camel@fedoraproject.org> References: <20180329180112.11055-1-labbott@redhat.com> <1522413619.15770.88.camel@fedoraproject.org> From: Masahiro Yamada Date: Mon, 7 May 2018 15:58:57 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFCv2 PATCH 0/3] Salted build ids via linker sections To: Mark Wielaard Cc: Laura Abbott , Andy Lutomirski , "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 21:40 GMT+09:00 Mark Wielaard : > 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. Indeed. This series is easier than --build-id-salt. If you do not see any better solution, I can accept this. BTW, when I read https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo I thought "we could reverse the symlink direction from debug file to build-id file)" sensible (but I understand it is not easy to change this way). If two packages share an identical image, one package can borrow the image from the other, then the storage space will be saved. So, having identical ID should be advantage, but we actually see only disadvantage... > 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". > -- Best Regards Masahiro Yamada