From: Finn Thain <fthain@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: linux-m68k@vger.kernel.org, geert@linux-m68k.org,
Andreas Schwab <schwab@linux-m68k.org>,
Stan Johnson <userm57@yahoo.com>
Subject: Re: [PATCH RFC v1] m68k: signal.c: use signal frame gap to avoid stack corruption
Date: Sun, 30 Apr 2023 19:24:40 +1000 (AEST) [thread overview]
Message-ID: <bf82f602-24b8-7b8d-899c-90dc55c910e0@linux-m68k.org> (raw)
In-Reply-To: <2458d3f7-4ad9-d4eb-4bf2-034ce8e3a94c@gmail.com>
On Sun, 30 Apr 2023, Michael Schmitz wrote:
>
> A fixed offset, or skipping signal delivery entirely is much the easiest
> solution for now.
>
I agree -- if address errors don't produce an unreliable USP then skipping
signal delivery on bus errors seems like the best solution (given that RAM
is so limited).
prev parent reply other threads:[~2023-04-30 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 8:04 [PATCH RFC v1] m68k: signal.c: use signal frame gap to avoid stack corruption Michael Schmitz
2023-04-29 8:17 ` Andreas Schwab
2023-04-29 9:01 ` Michael Schmitz
2023-04-29 9:49 ` Finn Thain
2023-04-29 20:08 ` Michael Schmitz
2023-04-30 0:24 ` Finn Thain
2023-04-30 7:56 ` Michael Schmitz
2023-04-30 9:24 ` Finn Thain [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=bf82f602-24b8-7b8d-899c-90dc55c910e0@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.com \
--cc=schwab@linux-m68k.org \
--cc=userm57@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox