linux-kernel - Re: [PATCH] kallsyms: Don't let kallsyms_lookup_size_offset() fail on retrieving the first symbol

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190826104638.9098e6fe940ffe19d24959a2@kernel.org>
Date:   Mon, 26 Aug 2019 10:46:38 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     Marc Zyngier <maz@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Arnaldo Carvalho de Melo <acme@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Will Deacon <will@...nel.org>,
        Catalin Marinas <catalin.marinas@....com>
Subject: Re: [PATCH] kallsyms: Don't let kallsyms_lookup_size_offset() fail
 on retrieving the first symbol

On Sat, 24 Aug 2019 14:12:31 +0100
Marc Zyngier <maz@...nel.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@...nel.org>

Thank you,

> 
> Fixes: ffc5089196446 ("[PATCH] Create kallsyms_lookup_size_offset()")
> Cc: Masami Hiramatsu <mhiramat@...nel.org>
> Cc: Arnaldo Carvalho de Melo <acme@...hat.com>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: Will Deacon <will@...nel.org>
> Cc: Catalin Marinas <catalin.marinas@....com>
> Signed-off-by: Marc Zyngier <maz@...nel.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@...nel.org>