From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH v2] m68k: save extra registers on more syscall entry points
Date: Fri, 18 Jun 2021 18:54:52 -0700 [thread overview]
Message-ID: <CAHk-=wjFG7zfO7RXu8RUOkuRPE59-OuqzBFsH-Zk1ieSKYbrYA@mail.gmail.com> (raw)
In-Reply-To: <2b2ba866-104c-afea-9c29-145e9d80c2d5@gmail.com>
On Fri, Jun 18, 2021 at 6:32 PM Michael Schmitz <schmitzmic@gmail.com> wrote:
>
> *** FORMAT ERROR *** FORMAT=0
> Current process id is 1
> BAD KERNEL TRAP: 00000000
> Modules linked in:
> PC: [<00002af0>] resume_userspace+0x14/0x16
> SR: 2204 SP: (ptrval) a2: 00000000
> d0: 00000000 d1: 00000000 d2: 00000000 d3: 00000000
> d4: 00000000 d5: 00000000 a0: 00000000 a1: 00000000
Yeah, so that's presumably the rte that causes an exception due to
garbage on the stack.
The registers being zero at that point is actually expected, so that's
not much of a hint. But yeah, clearly I got some stack initialization
offset or something wrong there, and I don't know modern m68k nearly
well enough to even guess where I screwed up.
Linus
next prev parent reply other threads:[~2021-06-19 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 1:27 [PATCH v2] m68k: save extra registers on more syscall entry points Michael Schmitz
2021-06-18 17:17 ` Linus Torvalds
2021-06-18 22:34 ` Michael Schmitz
2021-06-18 23:38 ` Linus Torvalds
2021-06-18 23:59 ` Michael Schmitz
2021-06-19 1:32 ` Michael Schmitz
2021-06-19 1:54 ` Linus Torvalds [this message]
2021-06-19 2:13 ` Linus Torvalds
2021-06-19 2:52 ` Michael Schmitz
2021-06-19 2:17 ` Michael Schmitz
2021-06-18 18:39 ` Eric W. Biederman
2021-06-18 19:06 ` Michael Schmitz
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='CAHk-=wjFG7zfO7RXu8RUOkuRPE59-OuqzBFsH-Zk1ieSKYbrYA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.com \
--cc=schwab@linux-m68k.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 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.