public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
* [PATCH RFC 0/4]
@ 2024-02-04 19:21 Michael Schmitz
  2024-02-04 19:21 ` [PATCH RFC 1/4] m68k: Handle arrivals of multiple signals correctly Michael Schmitz
                   ` (4 more replies)
  0 siblings, 5 replies; 8+ messages in thread
From: Michael Schmitz @ 2024-02-04 19:21 UTC (permalink / raw)
  To: linux-m68k; +Cc: geert, uli, fthain, viro

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
   


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2024-02-05  6:03 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-02-04 19:21 [PATCH RFC 0/4] Michael Schmitz
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox