From: Finn Thain <fthain@linux-m68k.org>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@vger.kernel.org, geert@linux-m68k.org,
linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH v4 1/2] m68k: Handle __generic_copy_to_user faults more carefully
Date: Thu, 8 Aug 2024 16:56:51 +1000 (AEST) [thread overview]
Message-ID: <727be0d7-a3ed-d3eb-2a13-c6ac316cd25d@linux-m68k.org> (raw)
In-Reply-To: <ae5facc5-4b10-481b-9f76-f9b007309d8f@linux-m68k.org>
On Thu, 8 Aug 2024, Greg Ungerer wrote:
> On 8/8/24 11:57, Finn Thain wrote:
> >
> > >
> > > I'm afraid I've lost track of where we're at with this patch series.
> > > Does it need more work, or more bug reports such as the one below?
> >
> > Apparently the series is waiting for some testing on a Coldfire system
> > with MMU.
>
> Ok, I am in a state that I can do that now (I managed to fix my M5475EVB
> board).
Thanks, Greg.
> If I test the v4 versions of this patch set that should do the job?
>
There are 3 patches that need some more testing, one from me and two from
Michael:
[PATCH] m68k: Handle put_user() faults more carefully
[PATCH v4 1/2] m68k: Handle __generic_copy_to_user faults more carefully
[PATCH v4 2/2] m68k: improve __constant_copy_to_user_asm() fault handling
They were posted in two threads:
https://lore.kernel.org/linux-m68k/1ed9c4c753395510c1a8df9c35e2ad4c31c90f95.1714265926.git.fthain@linux-m68k.org/T/
https://lore.kernel.org/linux-m68k/CAMuHMdVrOnOQwCxk42YCjEkbfL-YDSvpf_xTaouv9hUs2bO+qg@mail.gmail.com/T/
On 680x0, one of the bugs was brought to light with 'stress-ng
--sysbadaddr -1'. The others required special test programs.
I've no idea whether Coldfire silicon is susceptable at all, and if it is,
whether the same reproducers would work. But that's neither here nor there
from a regression testing standpoint.
next prev parent reply other threads:[~2024-08-08 6:56 UTC|newest]
Thread overview: 17+ 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-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 [this message]
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=727be0d7-a3ed-d3eb-2a13-c6ac316cd25d@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox