From: Masami Hiramatsu <mhiramat@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] kallsyms: Don't let kallsyms_lookup_size_offset() fail on retrieving the first symbol
Date: Mon, 26 Aug 2019 10:46:38 +0900 [thread overview]
Message-ID: <20190826104638.9098e6fe940ffe19d24959a2@kernel.org> (raw)
In-Reply-To: <20190824131231.26399-1-maz@kernel.org>
On Sat, 24 Aug 2019 14:12:31 +0100
Marc Zyngier <maz@kernel.org> wrote:
> An arm64 kernel configured with
>
> CONFIG_KPROBES=y
> CONFIG_KALLSYMS=y
> # CONFIG_KALLSYMS_ALL is not set
> CONFIG_KALLSYMS_BASE_RELATIVE=y
>
> reports the following kprobe failure:
>
> [ 0.032677] kprobes: failed to populate blacklist: -22
> [ 0.033376] Please take care of using kprobes.
>
> It appears that kprobe fails to retrieve the symbol at address
> 0xffff000010081000, despite this symbol being in System.map:
>
> ffff000010081000 T __exception_text_start
>
> This symbol is part of the first group of aliases in the
> kallsyms_offsets array (symbol names generated using ugly hacks in
> scripts/kallsyms.c):
>
> kallsyms_offsets:
> .long 0x1000 // do_undefinstr
> .long 0x1000 // efi_header_end
> .long 0x1000 // _stext
> .long 0x1000 // __exception_text_start
> .long 0x12b0 // do_cp15instr
>
> Looking at the implementation of get_symbol_pos(), it returns the
> lowest index for aliasing symbols. In this case, it return 0.
>
> But kallsyms_lookup_size_offset() considers 0 as a failure, which
> is obviously wrong (there is definitely a valid symbol living there).
> In turn, the kprobe blacklisting stops abruptly, hence the original
> error.
>
> A CONFIG_KALLSYMS_ALL kernel wouldn't fail as there is always
> some random symbols at the beginning of this array, which are never
> looked up via kallsyms_lookup_size_offset.
>
> Fix it by considering that get_symbol_pos() is always successful
> (which is consistent with the other uses of this function).
Thank you for fixing this issue!
This looks good to me :)
Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
Thank you,
>
> Fixes: ffc5089196446 ("[PATCH] Create kallsyms_lookup_size_offset()")
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Will Deacon <will@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> ---
> kernel/kallsyms.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/kallsyms.c b/kernel/kallsyms.c
> index 95a260f9214b..136ce049c4ad 100644
> --- a/kernel/kallsyms.c
> +++ b/kernel/kallsyms.c
> @@ -263,8 +263,10 @@ int kallsyms_lookup_size_offset(unsigned long addr, unsigned long *symbolsize,
> {
> char namebuf[KSYM_NAME_LEN];
>
> - if (is_ksym_addr(addr))
> - return !!get_symbol_pos(addr, symbolsize, offset);
> + if (is_ksym_addr(addr)) {
> + get_symbol_pos(addr, symbolsize, offset);
> + return 1;
> + }
> return !!module_address_lookup(addr, symbolsize, offset, NULL, namebuf) ||
> !!__bpf_address_lookup(addr, symbolsize, offset, namebuf);
> }
> --
> 2.20.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2019-08-26 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 13:12 [PATCH] kallsyms: Don't let kallsyms_lookup_size_offset() fail on retrieving the first symbol Marc Zyngier
2019-08-26 1:46 ` Masami Hiramatsu [this message]
2019-08-27 10:08 ` Will Deacon
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=20190826104638.9098e6fe940ffe19d24959a2@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.