From: Michael Ellerman <mpe@ellerman.id.au>
To: bugzilla-daemon@bugzilla.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [Bug 213837] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5
Date: Wed, 08 Sep 2021 22:54:43 +1000 [thread overview]
Message-ID: <87ee9zmdm4.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <bug-213837-206035-BEt4KJvSST@https.bugzilla.kernel.org/>
bugzilla-daemon@bugzilla.kernel.org writes:
> https://bugzilla.kernel.org/show_bug.cgi?id=213837
>
> Erhard F. (erhard_f@mailbox.org) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> See Also|https://bugzilla.kernel.org |
> |/show_bug.cgi?id=213079 |
>
> --- Comment #4 from Erhard F. (erhard_f@mailbox.org) ---
> Checked out whether this has really something to do with bug #213079 or not by
> copying this root partition to a regular HDD and use that one instead. As the
> issue still happens it seems these are two seperate bugs.
>
> [...]
> Kernel panic - not syncing: corrupted stack end detected inside scheduler
Can you try this patch, it might help us work out what is corrupting the
stack.
cheers
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index c4462c454ab9..07bfa25c1b48 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -5490,8 +5490,14 @@ static noinline void __schedule_bug(struct task_struct *prev)
static inline void schedule_debug(struct task_struct *prev, bool preempt)
{
#ifdef CONFIG_SCHED_STACK_END_CHECK
- if (task_stack_end_corrupted(prev))
+ if (task_stack_end_corrupted(prev)) {
+ char *start = (char *)end_of_stack(prev);
+ pr_err("stack corrupted? stack end = 0x%px\n", end_of_stack(prev));
+ print_hex_dump(KERN_ERR, "stack: ", DUMP_PREFIX_ADDRESS, 16, 4,
+ start - SZ_1K, THREAD_SIZE + SZ_1K, true);
+
panic("corrupted stack end detected inside scheduler\n");
+ }
if (task_scs_end_corrupted(prev))
panic("corrupted shadow stack detected inside scheduler\n");
next prev parent reply other threads:[~2021-09-08 12:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 20:00 [Bug 213837] New: "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5 bugzilla-daemon
2021-07-23 20:01 ` [Bug 213837] " bugzilla-daemon
2021-08-20 16:34 ` bugzilla-daemon
2021-08-20 16:35 ` bugzilla-daemon
2021-09-05 14:11 ` bugzilla-daemon
2021-09-08 12:54 ` Michael Ellerman [this message]
2021-09-05 14:15 ` bugzilla-daemon
2021-09-08 12:54 ` bugzilla-daemon
2021-09-13 7:16 ` bugzilla-daemon
2021-09-13 7:16 ` bugzilla-daemon
2021-09-22 15:33 ` bugzilla-daemon
2021-09-23 14:05 ` Michael Ellerman
2021-09-23 14:05 ` bugzilla-daemon
2021-09-23 16:29 ` bugzilla-daemon
2021-09-24 22:16 ` bugzilla-daemon
2021-09-24 22:17 ` bugzilla-daemon
2021-09-24 22:25 ` bugzilla-daemon
2021-11-28 14:20 ` bugzilla-daemon
2022-01-22 0:07 ` bugzilla-daemon
2022-01-22 0:14 ` [Bug 213837] [bisected] " bugzilla-daemon
2022-02-19 23:29 ` bugzilla-daemon
2022-02-19 23:31 ` bugzilla-daemon
2022-03-13 11:32 ` bugzilla-daemon
2022-03-13 11:33 ` bugzilla-daemon
2022-03-13 11:34 ` bugzilla-daemon
2022-07-07 10:27 ` bugzilla-daemon
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=87ee9zmdm4.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).