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] m68k: Handle put_user() faults more carefully
Date: Mon, 4 May 2026 19:05:01 +1000 (AEST) [thread overview]
Message-ID: <fb2ca693-1f99-2c5a-7ff0-9bcf22f89de0@linux-m68k.org> (raw)
In-Reply-To: <1ed9c4c753395510c1a8df9c35e2ad4c31c90f95.1714265926.git.fthain@linux-m68k.org>
ping...
On Sun, 28 Apr 2024, Finn Thain wrote:
> Running 'stress-ng --sysbadaddr -1' on my MC68040 system immediately
> produces an oops:
>
> Unable to handle kernel access at virtual address f1c422fb
> Oops: 00000000
> Modules linked in:
> PC: [<00005a1a>] do_040writeback1+0xae/0x160
> SR: 2010 SP: 96087dc2 a2: 01500000
> d0: 00000000 d1: 014e8000 d2: 00000081 d3: 00000000
> d4: 00000481 d5: c043dfff a0: 014e8000 a1: 00632fd5
> Process stress-ng (pid: 221, task=1b729d30)
> Frame format=7 eff addr=014e9eb8 ssw=0c81 faddr=c043dfff
> wb 1 stat/addr/data: 0001 00000481 c043dfff
> wb 2 stat/addr/data: 0081 c043dfff 2f746d70
> wb 3 stat/addr/data: 0005 014e9ed4 2f746d70
> push data: c043dfff 800daa70 00000000 014e9f1c
> Stack from 014e9ed4:
> 2f740000 8017c000 014e9f10 00006830 00000081 c043dfff 2f746d70 2f746d70
> 0081a000 00000400 c043dfff 800daa70 c043dfff 80016a20 00000003 014e9f88
> 000026c8 014e9f1c 00000001 2f746d70 0081a000 00000400 c043dfff 0081afff
> c043dfff 01500000 00000001 ffffffff 00000000 20000046 41d67008 014e9f58
> 04810005 00810045 c043dfff 014e9f84 2f746d70 c043dfff 2f746d70 c043dfff
> 80016a20 8017c000 00000000 0081affb 00000005 014e9fc4 00128bc6 c043dfff
> Call Trace: [<00006830>] buserr_c+0x510/0x698
> [<000026c8>] buserr+0x20/0x28
> [<00128bc6>] sys_getcwd+0xc8/0x15a
> [<000027a2>] syscall+0x8/0xc
> [<0008800d>] sanity_check_segment_list+0x17/0x11e
>
> Code: 000c 0e90 1800 220f 0281 ffff e000 2041 <2228> 0008 0281 00ff
> ff00 67a4 6026 4280 122e 0013 206e 000c 0e10 1800 220f 0281
>
> The cause is a deliberately misaligned access in the 'bad_end_addr' test
> case in the 'sysbadaddr' stressor. The location being accessed here,
> 0xc043dfff, was contrived to span the boundary between a r/w anonymous page
> and an unmapped page. The address was then passed to the getcwd syscall
> which faulted in copy_to_user().
>
> The fault for the mapped page appears to be handled okay -- up until
> do_040writeback1() called put_user() which produced a second fault due to
> the unmapped page.
>
> Michael Schmitz helpfully deciphered the oops and explained the exception
> processing leading up to it.
>
> "regs->pc does point to the PC in the format 7 frame which is the PC
> the fault was detected at, but not (in case of a writeback fault)
> the PC of the faulting instruction [that is, MOVES.L].
>
> "The writeback would still cross the page boundary, and fault if the
> unmapped page still isn't present. We would not see the PC of the
> movesl in that case, and fail to find the PC in the exception
> table."
>
> One solution is to add a NOP instruction after the MOVES.L to flush the
> pipeline and take the fault. That way, the PC value in the exception frame
> becomes dependable so the exception table works.
>
> Theoretically, there seems to be another bug in the existing code. If
> the instruction following the MOVES faulted, then after the fixup,
> execution would resume at the instruction which caused the fault. This
> appears to be a loop. After this patch, that cannot happen.
>
> Cc: Michael Schmitz <schmitzmic@gmail.com>
> Reviewed-and-tested-by: Michael Schmitz <schmitzmic@gmail.com>
> Signed-off-by: Finn Thain <fthain@linux-m68k.org>
> ---
>
> So far this has only been tested on Motorola 68030 and 68040 systems
> and still needs testing on the other MMU-enabled processors.
>
> I don't know whether or not get_user() has the same problem. Hence this
> patch is confined to put_user().
>
> No change since RFC patch.
> ---
> arch/m68k/include/asm/uaccess.h | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/arch/m68k/include/asm/uaccess.h b/arch/m68k/include/asm/uaccess.h
> index 64914872a5c9..44e52d8323e5 100644
> --- a/arch/m68k/include/asm/uaccess.h
> +++ b/arch/m68k/include/asm/uaccess.h
> @@ -31,11 +31,12 @@
> #define __put_user_asm(inst, res, x, ptr, bwl, reg, err) \
> asm volatile ("\n" \
> "1: "inst"."#bwl" %2,%1\n" \
> - "2:\n" \
> + "2: nop\n" \
> + "3:\n" \
> " .section .fixup,\"ax\"\n" \
> " .even\n" \
> "10: moveq.l %3,%0\n" \
> - " jra 2b\n" \
> + " jra 3b\n" \
> " .previous\n" \
> "\n" \
> " .section __ex_table,\"a\"\n" \
> @@ -53,11 +54,12 @@ do { \
> asm volatile ("\n" \
> "1: "inst".l %2,(%1)+\n" \
> "2: "inst".l %R2,(%1)\n" \
> - "3:\n" \
> + "3: nop\n" \
> + "4:\n" \
> " .section .fixup,\"ax\"\n" \
> " .even\n" \
> "10: movel %3,%0\n" \
> - " jra 3b\n" \
> + " jra 4b\n" \
> " .previous\n" \
> "\n" \
> " .section __ex_table,\"a\"\n" \
>
prev parent reply other threads:[~2026-05-04 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 0:58 [PATCH] m68k: Handle put_user() faults more carefully Finn Thain
2026-05-04 9:05 ` 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=fb2ca693-1f99-2c5a-7ff0-9bcf22f89de0@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