From: Finn Thain <fthain@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] m68k: Handle put_user faults more carefully
Date: Sat, 3 Oct 2026 15:30:09 +1000 (AEST) [thread overview]
Message-ID: <a62d1568-f59a-cd50-7518-12cf4ee54bd6@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdVbfUH1ZoFcS64t=gyE_cskMWv6gGvL8pjGirSGvAKu2w@mail.gmail.com>
On Fri, 2 Oct 2026, Geert Uytterhoeven wrote:
> > Reviewed-by: Michael Schmitz <schmitzmic@gmail.com>
> >
> > in case it helps.
> >
> > Anecdotally, I've seen similar uaccess faults causing kernel oops on 030
> > as well, so this may not merely be an artificial unaligned access issue.
>
> Shouldn't this include
> https://lore.kernel.org/20240429030945.22451-3-schmitzmic@gmail.com
> ?
>
I don't see a dependency on other patches. I think this patch stands on
its own merits. It fixes two bugs: one is an annoyance for those of us who
use stress-ng and the other bug is purely theoretical (thus far).
This fix can be merged independently of related bugs, even if those bugs
have similar fixes, because separate patches are usually preferable,
because a 'git revert' is usually a possibility.
prev parent reply other threads:[~2026-10-03 5:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 9:08 Finn Thain
2026-10-01 18:57 ` Michael Schmitz
2026-10-02 16:28 ` Geert Uytterhoeven
2026-10-02 23:55 ` Michael Schmitz
2026-10-03 1:23 ` Daniel Palmer
2026-10-05 12:42 ` Greg Ungerer
2026-10-07 23:54 ` Michael Schmitz
2026-10-08 13:41 ` Greg Ungerer
2026-10-09 6:56 ` Michael Schmitz
2026-10-12 13:23 ` Greg Ungerer
2026-10-12 17:42 ` Michael Schmitz
2026-10-03 5:30 ` 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=a62d1568-f59a-cd50-7518-12cf4ee54bd6@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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
all inboxes | Powered by JetHome®