[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240830062935.1187613-1-zhengyejian@huaweicloud.com>
Date: Fri, 30 Aug 2024 14:29:35 +0800
From: Zheng Yejian <zhengyejian@...weicloud.com>
To: arnd@...db.de,
masahiroy@...nel.org,
kees@...nel.org,
mcgrof@...nel.org,
jannh@...gle.com,
ardb@...nel.org,
song@...nel.org,
gregkh@...uxfoundation.org,
ojeda@...nel.org,
gary@...yguo.net,
wedsonaf@...gle.com
Cc: zhengyejian@...weicloud.com,
linux-kernel@...r.kernel.org
Subject: [RESEND PATCH] kallsyms: Fix wrong "big" kernel symbol type read from procfs
After commit 73bbb94466fd ("kallsyms: support "big" kernel symbols"),
ULEB128 was used to encode symbol name length. That is, for "big"
kernel symbols of which name length is longer than 0x7f characters,
the length info is encoded into 2 bytes.
kallsyms_get_symbol_type() expects to read the first char of the
symbol name which indicates the symbol type. However, due to the
"big" symbol case not being handled, the symbol type read from
/proc/kallsyms may be wrong, so handle it properly.
Fixes: 73bbb94466fd ("kallsyms: support "big" kernel symbols")
Signed-off-by: Zheng Yejian <zhengyejian@...weicloud.com>
---
Resend this patch due to no reply more than a month.
kernel/kallsyms.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/kernel/kallsyms.c b/kernel/kallsyms.c
index a9a0ca605d4a..9e4bf061bb83 100644
--- a/kernel/kallsyms.c
+++ b/kernel/kallsyms.c
@@ -103,8 +103,11 @@ static char kallsyms_get_symbol_type(unsigned int off)
{
/*
* Get just the first code, look it up in the token table,
- * and return the first char from this token.
+ * and return the first char from this token. If MSB of length
+ * is 1, it is a "big" symbol, so needs an additional byte.
*/
+ if (kallsyms_names[off] & 0x80)
+ off++;
return kallsyms_token_table[kallsyms_token_index[kallsyms_names[off + 1]]];
}
--
2.25.1
Powered by blists - more mailing lists