From: Huacai Chen <chenhuacai@kernel.org>
To: Enze Li <lienze@kylinos.cn>
Cc: kernel@xen0n.name, loongarch@lists.linux.dev, glider@google.com,
elver@google.com, akpm@linux-foundation.org,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
zhangqing@loongson.cn, yangtiezhu@loongson.cn,
dvyukov@google.com
Subject: Re: [PATCH 2/4 v2] LoongArch: Get stack without NMI when providing regs parameter
Date: Tue, 25 Jul 2023 15:40:27 +0800 [thread overview]
Message-ID: <CAAhV-H5nAwmjNsaA+=iR9EjrTSRogZUaoTcCULoe0YMgbAuFvg@mail.gmail.com> (raw)
In-Reply-To: <20230725061451.1231480-3-lienze@kylinos.cn>
Hi, Enze,
On Tue, Jul 25, 2023 at 2:15 PM Enze Li <lienze@kylinos.cn> wrote:
>
> Currently, arch_stack_walk() can only get the full stack information
> including NMI. This is because the implementation of arch_stack_walk()
> is forced to ignore the information passed by the regs parameter and use
> the current stack information instead.
>
> For some detection systems like KFENCE, only partial stack information
> is needed. In particular, the stack frame where the interrupt occurred.
>
> To support KFENCE, this patch modifies the implementation of the
> arch_stack_walk() function so that if this function is called with the
> regs argument passed, it retains all the stack information in regs and
> uses it to provide accurate information.
>
> Before the patch applied, I get,
> [ 1.531195 ] ==================================================================
> [ 1.531442 ] BUG: KFENCE: out-of-bounds read in stack_trace_save_regs+0x48/0x6c
> [ 1.531442 ]
> [ 1.531900 ] Out-of-bounds read at 0xffff800012267fff (1B left of kfence-#12):
> [ 1.532046 ] stack_trace_save_regs+0x48/0x6c
> [ 1.532169 ] kfence_report_error+0xa4/0x528
> [ 1.532276 ] kfence_handle_page_fault+0x124/0x270
> [ 1.532388 ] no_context+0x50/0x94
> [ 1.532453 ] do_page_fault+0x1a8/0x36c
> [ 1.532524 ] tlb_do_page_fault_0+0x118/0x1b4
> [ 1.532623 ] test_out_of_bounds_read+0xa0/0x1d8
> [ 1.532745 ] kunit_generic_run_threadfn_adapter+0x1c/0x28
> [ 1.532854 ] kthread+0x124/0x130
> [ 1.532922 ] ret_from_kernel_thread+0xc/0xa4
> <snip>
>
> With this patch applied, I get the correct stack information.
> [ 1.320220 ] ==================================================================
> [ 1.320401 ] BUG: KFENCE: out-of-bounds read in test_out_of_bounds_read+0xa8/0x1d8
> [ 1.320401 ]
> [ 1.320898 ] Out-of-bounds read at 0xffff800012257fff (1B left of kfence-#10):
> [ 1.321134 ] test_out_of_bounds_read+0xa8/0x1d8
> [ 1.321264 ] kunit_generic_run_threadfn_adapter+0x1c/0x28
> [ 1.321392 ] kthread+0x124/0x130
> [ 1.321459 ] ret_from_kernel_thread+0xc/0xa4
> <snip>
>
> Signed-off-by: Enze Li <lienze@kylinos.cn>
> ---
> arch/loongarch/kernel/stacktrace.c | 20 ++++++++++++++------
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/arch/loongarch/kernel/stacktrace.c b/arch/loongarch/kernel/stacktrace.c
> index 2463d2fea21f..9dab30ae68ec 100644
> --- a/arch/loongarch/kernel/stacktrace.c
> +++ b/arch/loongarch/kernel/stacktrace.c
> @@ -18,16 +18,24 @@ void arch_stack_walk(stack_trace_consume_fn consume_entry, void *cookie,
> struct pt_regs dummyregs;
> struct unwind_state state;
>
> - regs = &dummyregs;
We can move the 'if (regs)' logic here and simplify the whole function.
Huacai
> -
> if (task == current) {
> - regs->regs[3] = (unsigned long)__builtin_frame_address(0);
> - regs->csr_era = (unsigned long)__builtin_return_address(0);
> + if (regs)
> + memcpy(&dummyregs, regs, sizeof(*regs));
> + else {
> + dummyregs.regs[3] = (unsigned long)__builtin_frame_address(0);
> + dummyregs.csr_era = (unsigned long)__builtin_return_address(0);
> + }
> } else {
> - regs->regs[3] = thread_saved_fp(task);
> - regs->csr_era = thread_saved_ra(task);
> + if (regs)
> + memcpy(&dummyregs, regs, sizeof(*regs));
> + else {
> + dummyregs.regs[3] = thread_saved_fp(task);
> + dummyregs.csr_era = thread_saved_ra(task);
> + }
> }
>
> + regs = &dummyregs;
> +
> regs->regs[1] = 0;
> for (unwind_start(&state, task, regs);
> !unwind_done(&state) && !unwind_error(&state); unwind_next_frame(&state)) {
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-07-25 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:14 [PATCH 0/4 v2] Add KFENCE support for LoongArch Enze Li
2023-07-25 6:14 ` [PATCH 1/4 v2] LoongArch: mm: Add page table mapped mode support Enze Li
2023-07-25 7:38 ` Huacai Chen
2023-07-25 6:14 ` [PATCH 2/4 v2] LoongArch: Get stack without NMI when providing regs parameter Enze Li
2023-07-25 7:40 ` Huacai Chen [this message]
2023-07-26 2:59 ` Jinyang He
2023-07-28 6:57 ` Enze Li
2023-07-25 6:14 ` [PATCH 3/4 v2] KFENCE: Defer the assignment of the local variable addr Enze Li
2023-07-25 7:45 ` Huacai Chen
2023-07-25 6:14 ` [PATCH 4/4 v2] LoongArch: Add KFENCE support Enze Li
2023-07-25 7:48 ` Huacai Chen
2023-07-25 14:34 ` Jackie Liu
2023-07-28 6:01 ` Enze Li
2023-07-27 1:26 ` Huacai Chen
2023-07-28 3:27 ` Enze Li
2023-07-28 4:33 ` Huacai Chen
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='CAAhV-H5nAwmjNsaA+=iR9EjrTSRogZUaoTcCULoe0YMgbAuFvg@mail.gmail.com' \
--to=chenhuacai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel@xen0n.name \
--cc=lienze@kylinos.cn \
--cc=linux-mm@kvack.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@loongson.cn \
--cc=zhangqing@loongson.cn \
/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