From: "chenjun (AM)" <chenjun102@huawei.com>
To: "chenjun (AM)" <chenjun102@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "gregory.herrero@oracle.com" <gregory.herrero@oracle.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"Xiangrui (Euler)" <rui.xiang@huawei.com>
Subject: 答复: [PATCH] recordmcount: use w8 to read relp->r_info in arm64_is_fake_mcount
Date: Mon, 22 Feb 2021 15:50:19 +0000 [thread overview]
Message-ID: <CE1E7D7EFA066443B6454A6A5063B50220C5B320@dggeml509-mbx.china.huawei.com> (raw)
In-Reply-To: <20210222135840.56250-1-chenjun102@huawei.com>
Hi
There is no problem when I use aarch64_be(gcc v10.2). Because gcc v10.2 use __patchable_function_entries
instead of __mcount. I am not sure when the change happened.
Regards,
Chen Jun
-----邮件原件-----
发件人: Chen Jun [mailto:chenjun102@huawei.com]
发送时间: 2021年2月22日 21:59
收件人: linux-kernel@vger.kernel.org
抄送: gregory.herrero@oracle.com; catalin.marinas@arm.com; rostedt@goodmis.org; Xiangrui (Euler) <rui.xiang@huawei.com>
主题: [PATCH] recordmcount: use w8 to read relp->r_info in arm64_is_fake_mcount
On little endian system, Use aarch64_be(gcc v7.3) downloaded from linaro.org to build image with CONFIG_CPU_BIG_ENDIAN = y, CONFIG_FTRACE = y, CONFIG_DYNAMIC_FTRACE = y.
gcc will create symbols of _mcount but recordmcount can not create mcount_loc for *.o.
aarch64_be-linux-gnu-objdump -r fs/namei.o | grep mcount
00000000000000d0 R_AARCH64_CALL26 _mcount ...
0000000000007190 R_AARCH64_CALL26 _mcount
The reason is than funciton arm64_is_fake_mcount can not work correctly.
A symbol of _mcount in *.o compiled with big endian compiler likes:
00 00 00 2d 00 00 01 1b
w(rp->r_info) will return 0x2d instead of 0x011b. Because w() takes uint32_t as parameter, which truncates rp->r_info.
Use w8() instead w() to read relp->r_info
Fixes: ea0eada45632 ("recordmcount: only record relocation of type R_AARCH64_CALL26 on arm64.")
Signed-off-by: Chen Jun <chenjun102@huawei.com>
---
scripts/recordmcount.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/recordmcount.c b/scripts/recordmcount.c index b9c2ee7ab43f..cce12e1971d8 100644
--- a/scripts/recordmcount.c
+++ b/scripts/recordmcount.c
@@ -438,7 +438,7 @@ static int arm_is_fake_mcount(Elf32_Rel const *rp)
static int arm64_is_fake_mcount(Elf64_Rel const *rp) {
- return ELF64_R_TYPE(w(rp->r_info)) != R_AARCH64_CALL26;
+ return ELF64_R_TYPE(w8(rp->r_info)) != R_AARCH64_CALL26;
}
/* 64-bit EM_MIPS has weird ELF64_Rela.r_info.
--
2.25.0
next prev parent reply other threads:[~2021-02-22 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 13:58 [PATCH] recordmcount: use w8 to read relp->r_info in arm64_is_fake_mcount Chen Jun
2021-02-22 15:50 ` chenjun (AM) [this message]
2021-02-23 22:26 ` Steven Rostedt
2021-02-24 3:12 ` chenjun (AM)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CE1E7D7EFA066443B6454A6A5063B50220C5B320@dggeml509-mbx.china.huawei.com \
--to=chenjun102@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=gregory.herrero@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rui.xiang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).