summaryrefslogtreecommitdiffstats
path: root/arch/m68k/q40
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2023-01-30 23:48:54 -0500
committerAl Viro <viro@zeniv.linux.org.uk>2023-03-02 12:30:08 -0500
commitbd75497a77ccae9a5e1b0f1a3fa8283d67b21f4c (patch)
tree81397d2da394c3c03d59ce974611336f2f033d0c /arch/m68k/q40
parentc9c3395d5e3dcc6daee66c6908354d47bf98cb0c (diff)
downloadlinux-stable-bd75497a77ccae9a5e1b0f1a3fa8283d67b21f4c.tar.gz
linux-stable-bd75497a77ccae9a5e1b0f1a3fa8283d67b21f4c.tar.bz2
linux-stable-bd75497a77ccae9a5e1b0f1a3fa8283d67b21f4c.zip
m68k: fix livelock in uaccess
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. Tested-by: Finn Thain <fthain@linux-m68k.org> Tested-by: Geert Uytterhoeven <geert@linux-m68k.org> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'arch/m68k/q40')
0 files changed, 0 insertions, 0 deletions