From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-m68k@vger.kernel.org, geert@linux-m68k.org
Cc: gerg@linux-m68k.org
Subject: [PATCH v4 0/2] m68k uaccess fault handling fixes
Date: Mon, 29 Apr 2024 15:09:43 +1200 [thread overview]
Message-ID: <20240429030945.22451-1-schmitzmic@gmail.com> (raw)
(Actually now) version 4 of fixes for uaccess fault handling
on 68030, tested on 68030 and 68040.
Patch 1 has one exception table entry fixed (residual
calculated in __generic_copy_to_user did not take into
account the number of longword transfers omitted due to a
fault) si as well as a final NOP added in __clear_user.
Patch 2 is unchanged from v3 (actually since RFC v1), now
has Tested-by tag by Finn Thain added.
These patches would still benefit from testing on 68060
and Coldfire.
Cheers,
Michael
next reply other threads:[~2024-04-29 3:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 3:09 Michael Schmitz [this message]
2024-04-29 3:09 ` [PATCH v4 1/2] m68k: Handle __generic_copy_to_user faults more carefully Michael Schmitz
2024-08-07 8:14 ` Finn Thain
2024-08-07 19:32 ` Michael Schmitz
2024-08-08 1:57 ` Finn Thain
2024-08-08 6:05 ` Greg Ungerer
2024-08-08 6:56 ` Finn Thain
2024-08-08 14:52 ` Greg Ungerer
2024-08-08 19:27 ` Michael Schmitz
2024-08-09 3:34 ` Finn Thain
2024-08-09 8:03 ` Michael Schmitz
2024-08-09 12:58 ` Greg Ungerer
2024-08-09 3:22 ` Finn Thain
2024-08-08 6:58 ` Michael Schmitz
2024-04-29 3:09 ` [PATCH v4 2/2] m68k: improve __constant_copy_to_user_asm() fault handling Michael Schmitz
2024-04-29 7:58 ` [PATCH v4 0/2] m68k uaccess fault handling fixes Greg Ungerer
2024-04-29 8:08 ` Geert Uytterhoeven
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=20240429030945.22451-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