From: Jiangfeng Xiao <xiaojiangfeng@huawei.com>
To: Kees Cook <keescook@chromium.org>
Cc: <linux@armlinux.org.uk>, <arnd@arndb.de>,
<rmk+kernel@armlinux.org.uk>, <haibo.li@mediatek.com>,
<angelogioacchino.delregno@collabora.com>,
<amergnat@baylibre.com>, <akpm@linux-foundation.org>,
<dave.hansen@linux.intel.com>, <douzhaolei@huawei.com>,
<gustavoars@kernel.org>, <jpoimboe@kernel.org>,
<kepler.chenxin@huawei.com>, <kirill.shutemov@linux.intel.com>,
<linux-hardening@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-arm-kernel@lists.infradead.org>,
<nixiaoming@huawei.com>, <peterz@infradead.org>,
<wangbing6@huawei.com>, <wangfangpeng1@huawei.com>,
<jannh@google.com>, <David.Laight@aculab.com>
Subject: Re: [PATCH] ARM: unwind: improve unwinders for noreturn case
Date: Wed, 20 Mar 2024 11:30:13 +0800 [thread overview]
Message-ID: <fb8c6e8f-de47-8cbc-e30a-60961f5ce7ad@huawei.com> (raw)
In-Reply-To: <202403191945.661DBCE8@keescook>
On 2024/3/20 10:46, Kees Cook wrote:
> On Wed, Mar 20, 2024 at 10:19:29AM +0800, Jiangfeng Xiao wrote:
>> This is an off-by-one bug which is common in unwinders,
>> due to the fact that the address on the stack points
>> to the return address rather than the call address.
>>
>> So, for example, when the last instruction of a function
>> is a function call (e.g., to a noreturn function), it can
>> cause the unwinder to incorrectly try to unwind from
>> the function after the callee.
>>
>> foo:
>> ...
>> bl bar
>> ... end of function and thus next function ...
>>
>> which results in LR pointing into the next function.
>>
>> Fixed this by subtracting 1 from frmae->pc in the call frame
>> (but not exception frames) like ORC on x86 does.
>>
>> Refer to the unwind_next_frame function in the unwind_orc.c
>>
>> Suggested-by: Josh Poimboeuf <jpoimboe@kernel.org>
>> Link: https://lkml.kernel.org/lkml/20240305175846.qnyiru7uaa7itqba@treble/
>> Signed-off-by: Jiangfeng Xiao <xiaojiangfeng@huawei.com>
>> ---
>> arch/arm/include/asm/stacktrace.h | 4 ----
>> arch/arm/kernel/stacktrace.c | 2 --
>> arch/arm/kernel/traps.c | 4 ++--
>> arch/arm/kernel/unwind.c | 18 +++++++++++++++---
>> 4 files changed, 17 insertions(+), 11 deletions(-)
>>
>> diff --git a/arch/arm/include/asm/stacktrace.h b/arch/arm/include/asm/stacktrace.h
>> index 360f0d2..07e4c16 100644
>> --- a/arch/arm/include/asm/stacktrace.h
>> +++ b/arch/arm/include/asm/stacktrace.h
>> @@ -21,9 +21,7 @@ struct stackframe {
>> struct llist_node *kr_cur;
>> struct task_struct *tsk;
>> #endif
>> -#ifdef CONFIG_UNWINDER_FRAME_POINTER
>> bool ex_frame;
>> -#endif
>> };
>>
>> static __always_inline
>> @@ -37,9 +35,7 @@ void arm_get_current_stackframe(struct pt_regs *regs, struct stackframe *frame)
>> frame->kr_cur = NULL;
>> frame->tsk = current;
>> #endif
>> -#ifdef CONFIG_UNWINDER_FRAME_POINTER
>> frame->ex_frame = in_entry_text(frame->pc);
>> -#endif
>> }
>>
>> extern int unwind_frame(struct stackframe *frame);
>> diff --git a/arch/arm/kernel/stacktrace.c b/arch/arm/kernel/stacktrace.c
>> index 620aa82..1abd4f9 100644
>> --- a/arch/arm/kernel/stacktrace.c
>> +++ b/arch/arm/kernel/stacktrace.c
>> @@ -154,9 +154,7 @@ static void start_stack_trace(struct stackframe *frame, struct task_struct *task
>> frame->kr_cur = NULL;
>> frame->tsk = task;
>> #endif
>> -#ifdef CONFIG_UNWINDER_FRAME_POINTER
>> frame->ex_frame = in_entry_text(frame->pc);
>> -#endif
>> }
>>
>> void arch_stack_walk(stack_trace_consume_fn consume_entry, void *cookie,
>> diff --git a/arch/arm/kernel/traps.c b/arch/arm/kernel/traps.c
>> index 3bad79d..b64e442 100644
>> --- a/arch/arm/kernel/traps.c
>> +++ b/arch/arm/kernel/traps.c
>> @@ -84,10 +84,10 @@ void dump_backtrace_entry(unsigned long where, unsigned long from,
>> printk("%sFunction entered at [<%08lx>] from [<%08lx>]\n",
>> loglvl, where, from);
>> #elif defined CONFIG_BACKTRACE_VERBOSE
>> - printk("%s[<%08lx>] (%ps) from [<%08lx>] (%pS)\n",
>> + pr_warn("%s[<%08lx>] (%ps) from [<%08lx>] (%pB)\n",
>> loglvl, where, (void *)where, from, (void *)from);
>
> This should stay printk("%s...", loglvl, ...) or loglvl should be
> dropped when converting to pr_warn():
>
> pr_warn([<%08lx>] (%ps) from [<%08lx>] (%pB)\n",
> where, (void *)where, from, (void *)from);
>
> Why did you want to force the "warn" log level?
>
Thank you for your review. I think I'm wrong.
The checkpatch.pl script reports the "WARNING: printk() should
include KERN_<LEVEL> facility level" warning.
That's why I changed printk to pr_warn.
I should change printk to printk(KERN_DEFAULT).
>> #else
>> - printk("%s %ps from %pS\n", loglvl, (void *)where, (void *)from);
>> + pr_warn("%s %ps from %pB\n", loglvl, (void *)where, (void *)from);
>
> Ditto.
>
> -Kees
>
next prev parent reply other threads:[~2024-03-20 3:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 1:39 [PATCH] usercopy: delete __noreturn from usercopy_abort Jiangfeng Xiao
2024-03-04 15:15 ` Jann Horn
2024-03-04 17:40 ` Kees Cook
2024-03-05 3:31 ` Jiangfeng Xiao
2024-03-05 9:32 ` Kees Cook
2024-03-05 11:38 ` Jiangfeng Xiao
2024-03-05 17:58 ` Josh Poimboeuf
2024-03-06 4:00 ` Jiangfeng Xiao
2024-03-06 9:52 ` Russell King (Oracle)
2024-03-06 16:02 ` Josh Poimboeuf
2024-03-09 14:58 ` David Laight
2024-03-18 4:01 ` Jiangfeng Xiao
2024-03-05 2:54 ` Jiangfeng Xiao
2024-03-05 3:12 ` Jiangfeng Xiao
2024-03-20 2:19 ` [PATCH] ARM: unwind: improve unwinders for noreturn case Jiangfeng Xiao
2024-03-20 2:46 ` Kees Cook
2024-03-20 3:30 ` Jiangfeng Xiao [this message]
2024-03-20 3:34 ` Matthew Wilcox
2024-03-20 3:46 ` Jiangfeng Xiao
2024-03-20 3:44 ` [PATCH v2] " Jiangfeng Xiao
2024-03-20 8:45 ` Russell King (Oracle)
2024-03-20 15:30 ` Jiangfeng Xiao
2024-03-20 19:40 ` Russell King (Oracle)
2024-03-21 9:44 ` Jiangfeng Xiao
2024-03-21 10:22 ` David Laight
2024-03-21 11:23 ` Russell King (Oracle)
2024-03-21 12:07 ` David Laight
2024-03-21 12:22 ` Russell King (Oracle)
2024-03-21 12:57 ` David Laight
2024-03-21 13:08 ` Russell King (Oracle)
2024-03-21 14:37 ` David Laight
2024-03-21 14:56 ` Russell King (Oracle)
2024-03-21 15:20 ` David Laight
2024-03-21 15:33 ` Russell King (Oracle)
2024-03-21 22:43 ` Ard Biesheuvel
2024-03-22 0:08 ` Russell King (Oracle)
2024-03-22 9:24 ` David Laight
2024-03-22 9:52 ` Russell King (Oracle)
2024-03-22 12:54 ` Jiangfeng Xiao
2024-03-22 14:16 ` David Laight
2024-03-20 15:41 ` [PATCH v3] " Jiangfeng Xiao
2024-03-20 19:42 ` Russell King (Oracle)
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=fb8c6e8f-de47-8cbc-e30a-60961f5ce7ad@huawei.com \
--to=xiaojiangfeng@huawei.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=dave.hansen@linux.intel.com \
--cc=douzhaolei@huawei.com \
--cc=gustavoars@kernel.org \
--cc=haibo.li@mediatek.com \
--cc=jannh@google.com \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=kepler.chenxin@huawei.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=nixiaoming@huawei.com \
--cc=peterz@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=wangbing6@huawei.com \
--cc=wangfangpeng1@huawei.com \
/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