From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E8614C43461 for ; Wed, 16 Sep 2020 00:24:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 97C4A206A4 for ; Wed, 16 Sep 2020 00:24:37 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="g3ys2ycL" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726828AbgIPAYf (ORCPT ); Tue, 15 Sep 2020 20:24:35 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:32241 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726835AbgIOOTx (ORCPT ); Tue, 15 Sep 2020 10:19:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1600179553; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=n3aUX7mu7tx6gj7x1oFhz0vW3IscnXgty1qPqJGepZ4=; b=g3ys2ycLPN16rSWrkmHvDOK7w5072vXPd9YWgjHjbGdQa52McJ8nWDXCdWoqTcEz/L/h58 mz8nMaLFdj3nQZW68VxUGoO9UsaAjbRorzOlfzXEOaYq4UT2LJPhwnajZ1AVX8o+/AtJRZ hjXIlNvYJxcUHYwXkBUfwY9cScvn988= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-523-YGq3duzSPTOF0IWEcsmPZA-1; Tue, 15 Sep 2020 10:17:06 -0400 X-MC-Unique: YGq3duzSPTOF0IWEcsmPZA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A75D381F026; Tue, 15 Sep 2020 14:17:04 +0000 (UTC) Received: from treble (ovpn-112-136.rdu2.redhat.com [10.10.112.136]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E252960FC2; Tue, 15 Sep 2020 14:17:03 +0000 (UTC) Date: Tue, 15 Sep 2020 09:17:01 -0500 From: Josh Poimboeuf To: Mark Wielaard Cc: peterz@infradead.org, Hugh Dickins , linux-kernel@vger.kernel.org, x86@kernel.org Subject: Re: Static call dependency on libelf version? Message-ID: <20200915141701.j5fnir63trpwqbfp@treble> References: <20200915093016.GV1362448@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 15, 2020 at 01:24:17PM +0200, Mark Wielaard wrote: > But all this is for ancient versions of elfutils libelf. So it is hard > to say and my memory might be failing. If someone can confirm 0.158 > (which is 6 years old) works fine I would pick that as minimum version, > otherwise simply go with 0.168 which is 4 years old and should be on > most systems by now. I just discovered elf_version(), I assume that would allow us to check and enforce the libelf version? -- Josh