Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3069191pxj; Mon, 7 Jun 2021 01:09:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy19cAWyJ5/Ft+F33b7fnPyOYWPYpx3zphyJ4OZStPVh4loNUOOOiGoUSGATjPlra67oh6y X-Received: by 2002:a05:6402:1e8b:: with SMTP id f11mr5825491edf.86.1623053346168; Mon, 07 Jun 2021 01:09:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623053346; cv=none; d=google.com; s=arc-20160816; b=u4DKVy/gmaSsm4h0BD8HYAQVPGU0evrWTOwmQmN/E0zABRD34AuzT9f6dDdP/FR6hn l2QBJ2nGkbMkjADXZ52IKd5Hh+G/LCp5WMYZACSITtJ10vGIttl0EUbpBc4qTiZ10TBN iNT311p19uvIZL8GAa0y7EDYaFIvIlYmfVA0427lF1dzW2DKzOTO8YMqdeA9J95ZNjb6 kKdZGQyMDi3BkDil6H6SbGZEXoy+yOD63a6G9fD9zbAuyVgQl4e+IuZSr5XBPH/2H7uL dVCyJd8j2eosjLm9BQbZOdkBaPXQgWBUZba2Cw1m4v8Adq23dCTqnbDNHNr2pWnib/HG kqZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=hmWoG6fL8WElciCQkvXLrP00+LOYFcBov43x5F/M3qk=; b=oLNGGcKCE99xLBmifJlUx/kHrlsg3cckU+idf+6ky5HO9+O0hd8Q4gqJQGcHj16VUI 0NOAQF/vGEJqoz0876PPB/hkKzxPbov6iF1uiFARhwIHEAYGWibSG7XeYRgPX/FDoseL 3nasf2/OGgoMyieb46n6LBaoY0Qm0U68XQkH6I/uD5LvlQtpW4UzrM7fC2pLRgT/os0k E7FNnJh9guU9QQXHFRq/dn93b29Hzk9rLxc7gcdH8dFBxtd1UiBirTdps6bMcaTiZFnP HrNQ8NqxedfRYDSa/lgf7rxOgvBJDpcdSB6NmckRV+9gMYw7ixEm2cXGGekJ3Z9BoXW4 afeA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=mediatek.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h3si11834265edq.233.2021.06.07.01.08.43; Mon, 07 Jun 2021 01:09:06 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=mediatek.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230127AbhFGIIW (ORCPT + 99 others); Mon, 7 Jun 2021 04:08:22 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:52318 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S229545AbhFGIIW (ORCPT ); Mon, 7 Jun 2021 04:08:22 -0400 X-UUID: 673bbc106cb44ec8aea280470bada0a3-20210607 X-UUID: 673bbc106cb44ec8aea280470bada0a3-20210607 Received: from mtkmbs10n1.mediatek.inc [(172.21.101.34)] by mailgw01.mediatek.com (envelope-from ) (Generic MTA with TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 256/256) with ESMTP id 1536300742; Mon, 07 Jun 2021 16:06:28 +0800 Received: from mtkcas11.mediatek.inc (172.21.101.40) by mtkmbs08n1.mediatek.inc (172.21.101.55) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 7 Jun 2021 16:06:26 +0800 Received: from mtksdccf07.mediatek.inc (172.21.84.99) by mtkcas11.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Mon, 7 Jun 2021 16:06:26 +0800 From: Mark-PK Tsai To: CC: , , , , , , , , Subject: Re: [PATCH] recordmcount: avoid using ABS symbol as reference Date: Mon, 7 Jun 2021 16:06:26 +0800 Message-ID: <20210607080626.32612-1-mark-pk.tsai@mediatek.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20210607074258.32322-1-mark-pk.tsai@mediatek.com> References: <20210607074258.32322-1-mark-pk.tsai@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain X-MTK: N Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > On Mon, 7 Jun 2021 at 08:59, Mark-PK Tsai wrote: > > > > > > > > On Mon, 7 Jun 2021 at 04:42, Mark-PK Tsai wrote: > > > > > > > > > > Avoid using ABS symbol, which won't be relocate, as reference. > > > > > > > > > > On arm64 platform, if there's shndx equals SHN_ABS(0xfff1). > > > > > > > > > > Section Headers: > > > > > [Nr] Name Type Address Off Size ES Flg Lk Inf Al > > > > > [65521] .text.n_tty_receive_buf PROGBITS 0000000000000000 3cdab520 000054 00 AX 0 0 4 > > > > > [65522] .rela.text.n_tty_receive_buf RELA 0000000000000000 3cdab578 000030 18 I 152076 65521 8 > > > > > > > > > > > > > A RELA section's r_info field points to the section to which it > > > > applies. This is why in the example above section #65522 points to > > > > section #65521. This has nothing to do with the numerical value of > > > > SHN_ABS. > > > > > > If the r_info of RELA section is 65521(0xfff1), > > Oh sorry, I mean sh_info here. > > > > find_secsym_ndx() will use it to find the base symbol. > > > > > > > But what does that have to do with the sh_info field of the RELA > > section's Elf_Shdr struct? IOW, what is the relevance of section > > #65521 here? > > > > So what I mean is the problem occur if the sh_info of a RELA section > is #65521. Actually the problem occur if the sh_info of a RELA section is in the special section index range(SHN_LORESERVE ~ SHN_HIRESERVE). Maybe I should add a is_shndx_special() to check this like scripts/mod/modpost.h did? > > > > And in the symbol search loop in find_secsym_ndx(), get_symindex will > > > return 0xfff1 if the symbol is in ABS section. > > > > > > In this case, find_secsym_ndx() will return a absolute symbol as > > > base, which won't be relocate, if an ABS symbol is found before the > > > real symbol in section 65521. > > > > > > > I see your point here. > > > > > > > > > > > find_secsym_ndx, which use r_info in rela section to find the reference > > sh_info. > > > > > > symbol, may take ABS symbol as base. > > > > > > > > > > Symbol table '.symtab' contains 453285 entries: > > > > > Num: Value Size Type Bind Vis Ndx Name > > > > > 6: 0000000000000002 0 NOTYPE LOCAL DEFAULT ABS section_count > > > > > > > > > > Which cause an invalid address in __mcount_loc. > > > > > > > > > > > > > Could you give a better account of the error you are trying to address? > > > > > > > > Also, arm64 no longer defines a section_count symbol (since v5.11), so > > > > please make sure that the diagnostics of the issue you are addressing > > > > are accurate for mainline. > > > > > > > > > > My kernel version is 5.4.61. > > > But as I explained, I suppose mainline also have this issue. > > > > > > > Mainline is what we work on. So please base your changes (and your > > commit log) on mainline. > > > > I understand it. > But the platform I can reproduce the problem is only support to 5.4 LTS now. > And port it to the latest mainline kernel have much more work to do, can I just > keep this commit log? Or just remove the example I posted in the commit messsage? > > > > > > > > > > > > Signed-off-by: Mark-PK Tsai > > > > > --- > > > > > scripts/recordmcount.h | 4 ++++ > > > > > 1 file changed, 4 insertions(+) > > > > > > > > > > diff --git a/scripts/recordmcount.h b/scripts/recordmcount.h > > > > > index f9b19524da11..9b69167fb7ff 100644 > > > > > --- a/scripts/recordmcount.h > > > > > +++ b/scripts/recordmcount.h > > > > > @@ -526,6 +526,10 @@ static int find_secsym_ndx(unsigned const txtndx, > > > > > for (symp = sym0, t = nsym; t; --t, ++symp) { > > > > > unsigned int const st_bind = ELF_ST_BIND(symp->st_info); > > > > > > > > > > + /* avoid absolute symbols */ > > > > > + if (symp->st_shndx == SHN_ABS) > > > > > + continue; > > > > > + > > > > > if (txtndx == get_symindex(symp, symtab, symtab_shndx) > > > > > /* avoid STB_WEAK */ > > > > > && (STB_LOCAL == st_bind || STB_GLOBAL == st_bind)) { >