Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3413496pxj; Mon, 14 Jun 2021 23:53:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwFzR+YtUkmS4JfJmibLRUMv3gbTUAzKoWbUHjagTIfdjiCT739ZeEGm+jJ7bgtkCyhMfv1 X-Received: by 2002:a05:6638:2190:: with SMTP id s16mr20069936jaj.133.1623739980269; Mon, 14 Jun 2021 23:53:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623739980; cv=none; d=google.com; s=arc-20160816; b=kAAeOkiK1sRPG0mlSHhFVH8Evti8QPvleBwyxqbzZ3m4wthgq+h1QzOQUX4pCAD7Ik dqx77P1PS5//SsSOHiY2M7sIBnEhim/vgteEo+A5D2Do6FWCC2yCw84dlzEFQ9At4dzx hsmae/u3PkSgW5BtCBzDawwfRUZtHKO+vYM/Z2gfQa3BXEjxN+/7Q3+71Nla3+41K4p2 MCcaXibiGkVwION9lJM9enOtYYn653m2FRAjiQf2HvNaBISJBiSLVgAygdjCZP6Yr5zE 2Q58jKMkUi/Z6LkflrMCb8lW3bm8vox2ueNzASmaPrD+zW+jD4sXhVx/89CFzTr1jYqY f+1w== 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=tafli2NuofTE5etbrviooiRM0Gq/bMFdtfh+oRlU9Ao=; b=WYdcUvs0o9J5DaFcUJhmmw3d3Z5/buQYu7iIF7gg99Irk+fNiAxgcGgYlgWriX3B0k Waui82WxoTZ9DXBht/kct2smGsKkwVDw6b/3jRTLrSokHNf3F8dWwEtSi2q2SxnG+ww7 VyavP7eCqnBAYqB55JuYNPbVWOPwQ80ZOYjKPbylD+Wbf6bQmisxJ6CQFFfOl/TyBMd4 8z14mltFCgIsGlJz2fGh30SD3WewYmSVU26jHiy+yhOlr9zgiSRwoN9kfJSPDcQ3KTRa vBo7JHMuvyYwADZtTfJwqpubuo6RICfx+Lfy9MfbXcAqKbJxtBPz1DFjAkzI3fmkUB7n dMaQ== 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 a2si18776395jal.44.2021.06.14.23.52.48; Mon, 14 Jun 2021 23:53:00 -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 S229977AbhFOGxs (ORCPT + 99 others); Tue, 15 Jun 2021 02:53:48 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:37420 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S229493AbhFOGxr (ORCPT ); Tue, 15 Jun 2021 02:53:47 -0400 X-UUID: c282a59e0cc94007bb756791991e096e-20210615 X-UUID: c282a59e0cc94007bb756791991e096e-20210615 Received: from mtkcas11.mediatek.inc [(172.21.101.40)] by mailgw01.mediatek.com (envelope-from ) (Generic MTA with TLSv1.2 ECDHE-RSA-AES256-SHA384 256/256) with ESMTP id 1436944670; Tue, 15 Jun 2021 14:51:41 +0800 Received: from mtkcas11.mediatek.inc (172.21.101.40) by mtkmbs05n2.mediatek.inc (172.21.101.140) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 15 Jun 2021 14:51:40 +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; Tue, 15 Jun 2021 14:51:40 +0800 From: Mark-PK Tsai To: CC: , , , , , , Subject: Re: linux-next: build failure after merge of the ftrace tree Date: Tue, 15 Jun 2021 14:51:40 +0800 Message-ID: <20210615065140.22032-1-mark-pk.tsai@mediatek.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20210610110638.7e84912d@oasis.local.home> References: <20210610110638.7e84912d@oasis.local.home> MIME-Version: 1.0 Content-Type: text/plain X-MTK: N Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > On Thu, 10 Jun 2021 10:26:39 +0200 > Peter Zijlstra wrote: > > > On Thu, Jun 10, 2021 at 06:08:25PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > After merging the ftrace tree, today's linux-next build (powerpc > > > allyesconfig) failed like this: > > > > > > Cannot find symbol for section 255: .text.opal_int_set_mfrr. > > > arch/powerpc/platforms/powernv/opal-call.o: failed > > > > > > and many more similar. > > > > > > Caused by commit > > > > > > 9e419de4c678 ("recordmcount: Correct st_shndx handling") > > > > Argh.. lemme try and reproduce :/ > > I'll go and revert this patch, and wait for a new version from Peter. > > Hmm, crap, this is also sent to Linus. I'll stop that too. > > -- Steve I found the the build fail is because PPC64 is big endian and this patch use st_shndx directyly. Here is the case which cause this problem: recordmcount search symbol for txtndx = 255(0xff), but the corresponding symbol has st_shndx = 0xff00(bit endian) which equals SHN_LORESERVE, so the updated get_symindex() return 0. I send the patch v2 to fix it. https://lore.kernel.org/lkml/20210615064720.21950-1-mark-pk.tsai@mediatek.com/ Below is the test environment I used: https://musl.cc/powerpc64-linux-musl-cross.tgz make allyesconfig CROSS_COMPILE=powerpc64-linux-musl- ARCH=powerpc make vmlinux CROSS_COMPILE=powerpc64-linux-musl- ARCH=powerpc