From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-m68k@vger.kernel.org
Cc: geert@linux-m68k.org, uli@fpond.eu, fthain@linux-m68k.org,
viro@zeniv.linux.org.uk
Subject: [PATCH RFC 0/4]
Date: Mon, 5 Feb 2024 08:21:01 +1300 [thread overview]
Message-ID: <20240204192105.5677-1-schmitzmic@gmail.com> (raw)
CIP v4.4 backport of Al Viro's misc. m68k signal handling and
page fault fixes.
The first three are a prerequisite for Finn Thain's 'm68k: Move
signal frame following exception on 68020/030' patch, and fix
the backport compile error seen in
https://lore.kernel.org/oe-kbuild-all/202401310920.sBSI4BHj-lkp@intel.com/
RFC version of these patches to give Geert and Al a chance to yell
at me in case I got details of these patches wrong. I don't claim
to understand signal handling in anywhere near the required level
of detail.
Tested on my 68030 Atari Falcon.
Cheers,
Michael
next reply other threads:[~2024-02-04 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 19:21 Michael Schmitz [this message]
2024-02-04 19:21 ` [PATCH RFC 1/4] m68k: Handle arrivals of multiple signals correctly Michael Schmitz
2024-02-04 19:21 ` [PATCH RFC 2/4] m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal Michael Schmitz
2024-02-04 19:21 ` [PATCH RFC 3/4] m68k: Leave stack mangling to asm wrapper of sigreturn() Michael Schmitz
2024-02-04 19:21 ` [PATCH RFC 4/4] m68k equivalent of 26178ec11ef3 "x86: mm: consolidate VM_FAULT_RETRY handling" If e.g. get_user() triggers a page fault and a fatal signal is caught, we might end up with handle_mm_fault() returning VM_FAULT_RETRY and not doing anything to page tables. In such case we must *not* return to the faulting insn - that would repeat the entire thing without making any progress; what we need instead is to treat that as failed (user) memory access Michael Schmitz
2024-02-05 5:32 ` John Paul Adrian Glaubitz
2024-02-05 6:03 ` Michael Schmitz
2024-02-04 19:42 ` [PATCH RFC 0/4] Michael Schmitz
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=20240204192105.5677-1-schmitzmic@gmail.com \
--to=schmitzmic@gmail.com \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uli@fpond.eu \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).