From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-m68k@vger.kernel.org, geert@linux-m68k.org
Cc: gerg@linux-m68k.org
Subject: [PATCH v3 0/2] m68k uaccess fault handling fixes
Date: Sat, 27 Apr 2024 20:48:13 +1200 [thread overview]
Message-ID: <20240427084815.1449-1-schmitzmic@gmail.com> (raw)
Version 4 of fixes for uaccess fault handling on 68030,
tested on 68030 and 68040.
Patch 1 has additional exception table entries as well as
a final NOP added - evidently, in some cases the fault PC
points more than a single instruction past the moves that
caused the fault.
Patch 2 is unchanged from RFC v2.
These patches would still benefit from testing on 68060
and Coldfire. Looking at access_error060, I would not expect
the 68060 to behave much different from the 68040 and in
particular, addition of exception table entries to not cause
any regression. Less confident for Coldfire.
Cheers,
Michael
next reply other threads:[~2024-04-27 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 8:48 Michael Schmitz [this message]
2024-04-27 8:48 ` [PATCH v3 1/2] m68k: Handle __generic_copy_to_user faults more carefully Michael Schmitz
2024-04-27 9:34 ` Finn Thain
2024-04-27 23:16 ` Michael Schmitz
2024-04-28 3:28 ` Finn Thain
2024-04-28 3:51 ` Michael Schmitz
2024-04-28 8:03 ` Finn Thain
2024-04-27 8:48 ` [PATCH v3 2/2] m68k: improve __constant_copy_to_user_asm() fault handling Michael Schmitz
2024-04-27 9: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=20240427084815.1449-1-schmitzmic@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@vger.kernel.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