From: Finn Thain <fthain@linux-m68k.org>
To: Daniel Palmer <daniel@0x0f.com>, Andreas Schwab <schwab@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Handle put_user() faults more carefully
Date: Sun, 10 May 2026 13:47:47 +1000 (AEST) [thread overview]
Message-ID: <c5bf4a4c-6756-26b5-36c5-062d66b10033@linux-m68k.org> (raw)
In-Reply-To: <CAFr9PX=V-Hw2yCw8x=++n8KA5Vbd=ZeFpFwJ6j_hJmRgHcpaeA@mail.gmail.com>
On Sat, 9 May 2026, Daniel Palmer wrote:
> On Mon, 4 May 2026 at 18:07, Finn Thain <fthain@linux-m68k.org> wrote:
> > >
> > > So far this has only been tested on Motorola 68030 and 68040 systems
> > > and still needs testing on the other MMU-enabled processors.
>
> Would testing on an 060 amiga be helpful?
Testing on 68060 hardware could be helpful (not emulators though). If the
NOP failed to solve the problem on some CPU device or other then we could
look for a more broadly applicable solution. I suppose there may be a
faster solution too. Perhaps an architecture expert could comment.
> I just need to run the stress-ng --sysbadaddr -1 thing before and after
> and collect the logs?
>
That would work. I've been using an old static build of stress-ng 0.12.12
but I imagine that newer versions would be just as effective. Note that
the stressor runs for one day by default. You can use ^C or set a
different duration with -t N.
prev parent reply other threads:[~2026-05-10 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 0:58 Finn Thain
2026-05-04 9:05 ` Finn Thain
2026-05-09 10:03 ` Daniel Palmer
2026-05-10 3:47 ` 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=c5bf4a4c-6756-26b5-36c5-062d66b10033@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=daniel@0x0f.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.com \
--cc=schwab@linux-m68k.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
all inboxes | Powered by JetHome®