From: Finn Thain <fthain@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org,
"Michael Schmitz" <schmitzmic@gmail.com>,
"Andreas Schwab" <schwab@linux-m68k.org>
Subject: [PATCH RFC 0/2] 68020/030 signal handling following exceptions
Date: Tue, 02 May 2023 16:50:27 +1000 [thread overview]
Message-ID: <cover.1683010227.git.fthain@linux-m68k.org> (raw)
These two patches remedy stack corruption on 68020/030 when delivering
signals following a bus error or (theoretically) an address error.
Finn Thain (2):
m68k: Don't deliver signals except at instruction boundary
m68k: Make allowance for signal delivery following an address error
arch/m68k/kernel/entry.S | 6 +++++-
arch/m68k/kernel/signal.c | 13 +++++++++----
arch/m68k/kernel/traps.c | 10 ++++++++--
3 files changed, 22 insertions(+), 7 deletions(-)
--
2.37.5
next reply other threads:[~2023-05-02 6:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 6:50 Finn Thain [this message]
2023-05-02 6:50 ` [PATCH RFC 2/2] m68k: Make allowance for signal delivery following an address error Finn Thain
2023-05-02 21:06 ` Michael Schmitz
2023-05-03 4:11 ` Finn Thain
2023-05-03 5:50 ` Michael Schmitz
2023-05-03 8:02 ` Finn Thain
2023-05-04 21:06 ` Michael Schmitz
2023-05-05 3:14 ` Finn Thain
2023-05-05 5:05 ` Michael Schmitz
2023-05-05 21:35 ` Michael Schmitz
2023-05-06 0:36 ` Finn Thain
2023-05-06 1:46 ` Michael Schmitz
2023-05-06 2:46 ` Finn Thain
2023-05-06 8:24 ` Michael Schmitz
2023-05-06 1:11 ` Finn Thain
2023-05-06 1:54 ` Michael Schmitz
2023-05-06 2:11 ` Finn Thain
2023-05-06 2:30 ` Michael Schmitz
2023-05-02 6:50 ` [PATCH RFC 1/2] m68k: Don't deliver signals except at instruction boundary Finn Thain
2023-05-02 16:51 ` Andreas Schwab
2023-05-02 20:15 ` Michael Schmitz
2023-05-03 3:22 ` Finn Thain
2023-05-03 3:24 ` Finn Thain
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=cover.1683010227.git.fthain@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=geert@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox