All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@unseen.parts>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Richard Henderson <richard.henderson@linaro.org>,
	Matt Turner <mattst88@gmail.com>, Oleg Nesterov <oleg@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Magnus Lindholm <linmag7@gmail.com>,
	linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] alpha: stack fixes
Date: Thu, 30 Jan 2025 15:33:33 +0100	[thread overview]
Message-ID: <Z5uNvYWCwBFuX-W7@minute> (raw)
In-Reply-To: <alpine.DEB.2.21.2501291541500.56843@angie.orcam.me.uk>

On Wed, Jan 29, 2025 at 04:02:26PM +0000, Maciej W. Rozycki wrote:
> On Wed, 29 Jan 2025, Ivan Kokshaysky wrote:
> 
> > Somehow we got away with it until recently, when we ended up with
> > a stack corruption in kernel/smp.c:smp_call_function_single() due to
> > its use of 32-byte aligned local data and the compiler doing clever
> > things allocating it on the stack.
> 
>  Thank you for doing this work.
> 
>  I'll review/verify your changes by hand and push them through GCC and
> glibc regression testing, which should hopefully pick any fallout without 
> having it buried among any intermittent failures, and report back.

Thanks!

>  However, would you please cc <stable@kernel.org> with your submission, v2 
> presumably, so as to have these changes backported?

Sure.

As I need to deal with bpf build failure, v2 is inevitable.

>  The thing is I find it quite a grave bug being fixed here, which has been 
> there for decades and triggering occasionally[1], and it might be the only 
> way for users of certain older systems to get a kernel with the fix 
> already applied.  As you may have been aware non-BWX Alpha support has 
> been removed and while I'm working on bringing it back, it will likely be 
> missing support for specific models such as Jensen there will be no kernel 
> developer to look after.  So getting an LTS kernel might be the only way 
> to get a stable system for some people.

Yes, I know about your work on non-BWX Alpha and highly appreciate it.

> References:
> 
> [1] "System fails to boot when CONFIG_SMP=y", 
>     <https://bugzilla.kernel.org/show_bug.cgi?id=213143>
> 
>   Maciej

Ivan.

      reply	other threads:[~2025-01-30 14:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29  9:43 [PATCH 0/4] alpha: stack fixes Ivan Kokshaysky
2025-01-29  9:43 ` [PATCH 1/4] alpha/uapi: do not expose kernel-only stack frame structures Ivan Kokshaysky
2025-01-29 18:32   ` John Paul Adrian Glaubitz
2025-01-29 19:59     ` Ivan Kokshaysky
2025-01-29  9:43 ` [PATCH 2/4] alpha: replace hardcoded stack offsets with autogenerated ones Ivan Kokshaysky
2025-01-29  9:43 ` [PATCH 3/4] alpha: make stack 16-byte aligned (most cases) Ivan Kokshaysky
2025-01-29  9:43 ` [PATCH 4/4] alpha: align stack for page fault and user unaligned trap handlers Ivan Kokshaysky
2025-01-29 10:06 ` [PATCH 0/4] alpha: stack fixes John Paul Adrian Glaubitz
2025-01-29 16:02 ` Maciej W. Rozycki
2025-01-30 14:33   ` Ivan Kokshaysky [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=Z5uNvYWCwBFuX-W7@minute \
    --to=ink@unseen.parts \
    --cc=arnd@arndb.de \
    --cc=linmag7@gmail.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=mattst88@gmail.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=richard.henderson@linaro.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.