From: Chen Zhongjin <chenzhongjin@huawei.com>
To: "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"ak@linux.intel.com" <ak@linux.intel.com>
Subject: Re: [PATCH] x86: profiling: Using generic unwinding in profile_pc
Date: Mon, 3 Apr 2023 09:24:19 +0800 [thread overview]
Message-ID: <dc0625d2-edaf-22fe-5eea-3088e95a2998@huawei.com> (raw)
In-Reply-To: <20230224021858.120078-1-chenzhongjin@huawei.com>
Just ping... Or has profile code already been obsoleted?
On 2023/2/24 10:18, chenzhongjin wrote:
> Syzbot has been reporting the problem of stack-out-of-bounds in
> profile_pc for a long time:
> https://syzkaller.appspot.com/bug?extid=84fe685c02cd112a2ac3
>
> profile_pc tries to get pc if current regs is inside lock function. For
> !CONFIG_FRAME_POINTER it used a hack way to get the pc from stack, which
> is not work with ORC. It makes profile_pc returns wrong result, and
> frequently triggers KASAN.
>
> This can be fixed by using the unwind_start, it will skip the first
> regs frame and get the caller of lock function directly, or 0 if
> unwind_get_return_address finds the unwinding failed. For all of FP, ORC
> and guess unwinders it works.
>
> Fixes: 0cb91a229364 ("[PATCH] i386: Account spinlocks to the caller during profiling for !FP kernels")
> Reported-by: syzbot+84fe685c02cd112a2ac3@syzkaller.appspotmail.com
> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
> ---
> arch/x86/kernel/time.c | 20 ++++++--------------
> 1 file changed, 6 insertions(+), 14 deletions(-)
>
> diff --git a/arch/x86/kernel/time.c b/arch/x86/kernel/time.c
> index e42faa792c07..5e0446f49906 100644
> --- a/arch/x86/kernel/time.c
> +++ b/arch/x86/kernel/time.c
> @@ -24,26 +24,18 @@
> #include <asm/timer.h>
> #include <asm/hpet.h>
> #include <asm/time.h>
> +#include <asm/unwind.h>
>
> unsigned long profile_pc(struct pt_regs *regs)
> {
> unsigned long pc = instruction_pointer(regs);
>
> if (!user_mode(regs) && in_lock_functions(pc)) {
> -#ifdef CONFIG_FRAME_POINTER
> - return *(unsigned long *)(regs->bp + sizeof(long));
> -#else
> - unsigned long *sp = (unsigned long *)regs->sp;
> - /*
> - * Return address is either directly at stack pointer
> - * or above a saved flags. Eflags has bits 22-31 zero,
> - * kernel addresses don't.
> - */
> - if (sp[0] >> 22)
> - return sp[0];
> - if (sp[1] >> 22)
> - return sp[1];
> -#endif
> + struct unwind_state state;
> +
> + /* unwind_start will skip the first regs frame */
> + unwind_start(&state, current, regs, NULL);
> + pc = unwind_get_return_address(&state);
> }
> return pc;
> }
next prev parent reply other threads:[~2023-04-03 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 2:18 Chen Zhongjin
2023-04-03 1:24 ` Chen Zhongjin [this message]
2023-04-03 18:29 ` Andi Kleen
2023-04-04 2:03 ` Chen Zhongjin
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=dc0625d2-edaf-22fe-5eea-3088e95a2998@huawei.com \
--to=chenzhongjin@huawei.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®