Received: by 10.213.65.68 with SMTP id h4csp290453imn; Fri, 30 Mar 2018 05:41:46 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+D3lGJWcyzbOnPkppZmwDv7l0U4S4mzT7vV+HMirvq1x8Tt5KT+KoBxwfhgI2K+GZ9kpHu X-Received: by 10.99.135.67 with SMTP id i64mr8372244pge.346.1522413706563; Fri, 30 Mar 2018 05:41:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522413706; cv=none; d=google.com; s=arc-20160816; b=s5uvISgsCnUa6G3q8bGF+0AP8i0MUSH/saHDn3sJFzhp6/Qb96AtTj+lB2dese7Zq0 1hS8rI/Js9ip11HB4Y573TR2RbEuu7Em4C0+kaJRmFP7Tzj4YVsPsPPOqYcFSVvV9hyx KLx0HMrcQzff/j+f2GgbeUREgCYONqFuum1m+3kUtPO/CcnVs203jY6NWT8hCAhuaRFp 3DNa85fPbvBSsnx6GuVgCT0981ocJy6fBCbYcaaOZjI+nprVVE6lJ8OSfBUXAj5KjYla UYbwzBXVYkodZWT8TtO9MaZ32DcX4Rkd8/wOJu9eeIlr4gzRTcHrCWQc1eHqHpFTEh/V B41Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=XJSNADsYmQEns73R5S+krnmkzDgwPrUFkehKAyTKmLg=; b=hwOIyzmyb+hZb5SjQeLsRGppk9DxStnKmaYSY46HANF+jksneULP418epP9fGwcgOz L/MWYqlWz47/G8vu2ro0MSrr26ZIUFM+rn4+tZkBr/pEVZS6eOzWmuPJiUgoyhd6qNPb YJ4XASV74sx6YDywwbudqWNwXxp/oEVuKe/IsRvWmAt1QLwEBMzLXb/JcAsGAs+OpRN0 LMaGwV2/RIaePlPikuY+UegSHEZvX2t5pq0eMlNZpHtQN+4o4THyJ2l5kilNMt2AEv8Q rJCFS35IT8g50qMJs/ZNJhj5AUFEvGdsSPTOoVo3qqYahflqGH5QI4uUoFy8zPGV9mfo tSEg== ARC-Authentication-Results: i=1; mx.google.com; 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 q22si5569638pgc.12.2018.03.30.05.41.31; Fri, 30 Mar 2018 05:41:46 -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; 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 S1751443AbeC3MkX convert rfc822-to-8bit (ORCPT + 99 others); Fri, 30 Mar 2018 08:40:23 -0400 Received: from wildebeest.demon.nl ([212.238.236.112]:40154 "EHLO gnu.wildebeest.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751230AbeC3MkW (ORCPT ); Fri, 30 Mar 2018 08:40:22 -0400 Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id E2980304D68D; Fri, 30 Mar 2018 14:40:19 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id C4FE140013BF; Fri, 30 Mar 2018 14:40:19 +0200 (CEST) Message-ID: <1522413619.15770.88.camel@fedoraproject.org> Subject: Re: [RFCv2 PATCH 0/3] Salted build ids via linker sections From: Mark Wielaard To: Laura Abbott , Andy Lutomirski , "H . J . Lu" , Masahiro Yamada Cc: Linus Torvalds , X86 ML , linux-kernel@vger.kernel.org, Nick Clifton , Cary Coutant , linux-kbuild@vger.kernel.org Date: Fri, 30 Mar 2018 14:40:19 +0200 In-Reply-To: <20180329180112.11055-1-labbott@redhat.com> References: <20180329180112.11055-1-labbott@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Mailer: Evolution 3.22.6 (3.22.6-10.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on gnu.wildebeest.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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