From: Oleg Nesterov <oleg@redhat.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Laight <David.Laight@ACULAB.COM>
Cc: Vernon Lovejoy <vlovejoy@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/show_trace_log_lvl: ensure stack pointer is aligned, again
Date: Thu, 4 May 2023 20:13:59 +0200 [thread overview]
Message-ID: <20230504181359.GA4932@redhat.com> (raw)
In-Reply-To: <20230429100955.GA20567@redhat.com>
Josh,
This version does exactly what you requested in reply to v1.
https://lore.kernel.org/lkml/20230428043158.r5omehiaqawcac2y@treble/
What else should we do? Make V3 following David's suggestion
https://lore.kernel.org/lkml/aa8537d81dc747a097e9e30491b5081b@AcuMS.aculab.com/
? Or what?
On 04/29, Oleg Nesterov wrote:
>
> From: Vernon Lovejoy <vlovejoy@redhat.com>
>
> The commit e335bb51cc15 ("x86/unwind: Ensure stack pointer is aligned")
> tried to align the stack pointer in show_trace_log_lvl(), otherwise the
> "stack < stack_info.end" check can't guarantee that the last read does
> not go past the end of the stack.
>
> However, we have the same problem with the initial value of the stack
> pointer, it can also be unaligned. So without this patch this trivial
> kernel module
>
> #include <linux/module.h>
>
> static int init(void)
> {
> asm volatile("sub $0x4,%rsp");
> dump_stack();
> asm volatile("add $0x4,%rsp");
>
> return -EAGAIN;
> }
>
> module_init(init);
> MODULE_LICENSE("GPL");
>
> crashes the kernel.
>
> Fixes: e335bb51cc15 ("x86/unwind: Ensure stack pointer is aligned")
> Signed-off-by: Vernon Lovejoy <vlovejoy@redhat.com>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> ---
> arch/x86/kernel/dumpstack.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/dumpstack.c b/arch/x86/kernel/dumpstack.c
> index 0bf6779187dd..f82d896eb99d 100644
> --- a/arch/x86/kernel/dumpstack.c
> +++ b/arch/x86/kernel/dumpstack.c
> @@ -195,7 +195,6 @@ static void show_trace_log_lvl(struct task_struct *task, struct pt_regs *regs,
> printk("%sCall Trace:\n", log_lvl);
>
> unwind_start(&state, task, regs, stack);
> - stack = stack ? : get_stack_pointer(task, regs);
> regs = unwind_get_entry_regs(&state, &partial);
>
> /*
> @@ -214,7 +213,10 @@ static void show_trace_log_lvl(struct task_struct *task, struct pt_regs *regs,
> * - hardirq stack
> * - entry stack
> */
> - for ( ; stack; stack = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
> + for (stack = PTR_ALIGN(stack ?: get_stack_pointer(task, regs), sizeof(long));
> + stack;
> + stack = PTR_ALIGN(stack_info.next_sp, sizeof(long)))
> + {
> const char *stack_name;
>
> if (get_stack_info(stack, task, &stack_info, &visit_mask)) {
> --
> 2.25.1.362.g51ebf55
>
prev parent reply other threads:[~2023-05-04 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 10:09 [PATCH v2] x86/show_trace_log_lvl: ensure stack pointer is aligned, again Oleg Nesterov
2023-05-04 18:13 ` Oleg Nesterov [this message]
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=20230504181359.GA4932@redhat.com \
--to=oleg@redhat.com \
--cc=David.Laight@ACULAB.COM \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vlovejoy@redhat.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 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.