From: Greg Ungerer <gerg@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@vger.kernel.org, geert@linux-m68k.org
Subject: Re: [PATCH v4 0/2] m68k uaccess fault handling fixes
Date: Mon, 29 Apr 2024 17:58:32 +1000 [thread overview]
Message-ID: <5d72bdb5-a98e-4b2a-99d0-73b592fe0993@linux-m68k.org> (raw)
In-Reply-To: <20240429030945.22451-1-schmitzmic@gmail.com>
Hi Michael,
On 29/4/24 13:09, Michael Schmitz wrote:
> (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.
I would very much like to test them on ColdFire. Unfortunately my only
ColdFire with MMU board (a M547xEVB) failed a couple of months back.
I am trying to find a replacement, but so far have not been able to get
my hands on one.
Maybe someone else out there has one they can test with?
Regards
Greg
next prev parent reply other threads:[~2024-04-29 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 3:09 [PATCH v4 0/2] m68k uaccess fault handling fixes Michael Schmitz
2024-04-29 3:09 ` [PATCH v4 1/2] m68k: Handle __generic_copy_to_user faults more carefully 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 ` Greg Ungerer [this message]
2024-04-29 8:08 ` [PATCH v4 0/2] m68k uaccess fault handling fixes 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=5d72bdb5-a98e-4b2a-99d0-73b592fe0993@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.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 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.