Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp587508ybm; Thu, 28 May 2020 10:05:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwiQaC/r5FPfwMgGX0DTKY/WOocYZeRBJFgR5OMRcY8GBLLP/YMnY8iqlVo0z90BnD+fXzw X-Received: by 2002:a50:e08c:: with SMTP id f12mr4157269edl.233.1590685528413; Thu, 28 May 2020 10:05:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590685528; cv=none; d=google.com; s=arc-20160816; b=H2Zu+OwriQrLEW/06GEcpavqnR6Nz8k/Iz/ajeaYkoHhqCUGD5quhtaGGgp/yc9GeT nhSUUGwi8uBUpY/w9+0S5SdnG6I63e4++5q6tiAaw2C35slKAXJICZf6LOkkX/htIjJS E2ryzq60VwD/gDrn7pcIyocXxT7XECoCotfzkYrX6C1w/ARdkWgFcjJ9dBfFtkS5Utsm Pri3f/0UHxw2t6F+1gYxzgWnsZ8cErXHK49RbQTDKEKkiL2LH4E28Yn6Qv57UNhOKoui NNj1PTemZbBcc335i1BAAhqwzfaEJDM+Jl3pTTt1wufNkVQ7gWGUlZAMHMGZoD3w2JhH pMYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=k0AbgdM89I1fch23T6oXHrlkE5eBQV/JX1tB7m1TZRI=; b=uYsfKTJfRiPFlk0E11O17CA1rJTKCPjiTgyNl3bMrpRvR/+6dB6zvAbc13p/d6SMZR 69pHmqftCPFF/7HXh4LFYpgwd38OUu6KgJMwq/olCOEZHO3DOQzNbm2jF7zKWJc/egRm TLMIQ2k0j10J1069oaQ06lNct2jvaUvcuhIXo5EG9JPArbpv495Fxme65v+EqTT7xWvD gmY5wQG2vlAtCzZAVtI8O+hV7cIxT1Jl+DhOogTs11/1gRSwwHZiTEi2Ah0ziHjGw4Mp CjWl7KJ3t5W0bgYyG3cSFoJ1qFxp7K7nR5cJY8/2FHD10ize7sU0nrv0fF6uTjUkn4/2 qHVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=d2TuXafH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id de11si4161585edb.246.2020.05.28.10.05.05; Thu, 28 May 2020 10:05:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=d2TuXafH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405268AbgE1RAT (ORCPT + 99 others); Thu, 28 May 2020 13:00:19 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:60733 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2405254AbgE1RAS (ORCPT ); Thu, 28 May 2020 13:00:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1590685216; 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=k0AbgdM89I1fch23T6oXHrlkE5eBQV/JX1tB7m1TZRI=; b=d2TuXafHBgTRGeBpvmUyU/pI9KJSX7ejwOSWDQm/7TRVU81kEGnK5yFtDz28IAKr+5HQlE DdxaHiD59VaOsPBb8S7+O+tXYadNbNZgUodTeqY19CUAKeS0w0figjVeNwv5lsEgVD9S1g hl2PihAU0ClbEIKPqbIsnW4kg3aKMA4= 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-371-ey1vtCkwMGKYtdV7WbWLtA-1; Thu, 28 May 2020 13:00:14 -0400 X-MC-Unique: ey1vtCkwMGKYtdV7WbWLtA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6A55B835B40; Thu, 28 May 2020 17:00:13 +0000 (UTC) Received: from treble (ovpn-117-65.rdu2.redhat.com [10.10.117.65]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B689610013DB; Thu, 28 May 2020 17:00:12 +0000 (UTC) Date: Thu, 28 May 2020 12:00:10 -0500 From: Josh Poimboeuf To: Matt Helsley Cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Steven Rostedt Subject: Re: [RFC][PATCH 2/3] objtool: Find relocation base section using sh_info Message-ID: <20200528170010.xe46x3tvz4npvovj@treble> References: <20200528140916.6crguzfpehf6lext@treble> <20200528160247.GW9040@rlwimi.vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200528160247.GW9040@rlwimi.vmware.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 28, 2020 at 09:02:47AM -0700, Matt Helsley wrote: > On Thu, May 28, 2020 at 09:09:16AM -0500, Josh Poimboeuf wrote: > > On Wed, May 27, 2020 at 09:42:32AM -0700, Matt Helsley wrote: > > > Currently objtool uses a naming heuristic to find the "base" > > > section to apply the relocation(s) to. The standard defines > > > the SHF_INFO_LINK flag (SHF => in the section header flags) > > > which indicates when the section header's sh_info field can > > > be used to find the necessary section. > > > > > > Warns when the heuristic is used as a fallback and changes > > > the name heuristic calculation to handle rela (explicit > > > addend) and now rel (implicit addend) relocations. > > > > Does this fallback case actually happen? > > Not that I could see. I was thinking about taking it out but > I haven't tried this set with clang or other toolchains. So > I was wondering if you think holding off before removing it > would be wise or if you'd rather just remove it. I just realized somebody already submitted an almost identical patch: https://lkml.kernel.org/r/20200421182501.149101-1-samitolvanen@google.com Which I'll be merging soon... so you can just drop this one. Then you can base your next version of this set on top of that patch, if it hasn't been merged yet. -- Josh