From: "Arnd Bergmann" <arnd@arndb.de>
To: "Florian Fuchs" <fuchsfl@gmail.com>,
linux-sh@vger.kernel.org,
"Yoshinori Sato" <yoshinori.sato@nifty.com>,
"Rich Felker" <dalias@libc.org>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: traps: Fix kernel unaligned access fixup in branch delay slots
Date: Fri, 23 Oct 2026 09:07:57 +0200 [thread overview]
Message-ID: <04cfcbc2-0021-4ba2-b3bf-0da3cc82d046@app.fastmail.com> (raw)
In-Reply-To: <20261022233410.2959823-1-fuchsfl@gmail.com>
On Fri, Oct 23, 2026, at 01:34, Florian Fuchs wrote:
> Commit 75d4d29549e5 ("sh: remove CONFIG_SET_FS support") converted the
> callers' set_fs(KERNEL_DS) sections, but missed copy_from_user() in
> handle_delayslot() which relied on the caller's address limit. This also
> broke delay slot instruction fetching through handle_trapped_io().
>
> Since the removal of set_fs(), access_ok() rejects kernel addresses, so
> the fetch always fails for kernel code and the kernel dies with:
>
> delay-slot-insn faulting in handle_unaligned_delayslot: 0000 [#1]
>
> The initial instruction fetch in do_address_error() already uses
> copy_from_kernel_nofault() for kernel mode. So choose the matching
> instruction-fetch accessor from user_mode(regs) and fetch the
> instruction.
>
> Fixes: 75d4d29549e5 ("sh: remove CONFIG_SET_FS support")
> Signed-off-by: Florian Fuchs <fuchsfl@gmail.com>
Hi Florian,
The patch looks correct to me, but I find it a little confusing:
> @@ -287,8 +287,10 @@ static inline int handle_delayslot(struct pt_regs *regs,
> insn_size_t instruction;
> void __user *addr = (void __user *)(regs->pc +
> instruction_size(old_instruction));
> + struct mem_access *insn_ma = user_mode(regs) ?
> + &user_mem_access : &kernel_mem_access;
>
> - if (copy_from_user(&instruction, addr, sizeof(instruction))) {
> + if (insn_ma->from(&instruction, addr, sizeof(instruction))) {
> /* the instruction-fetch faulted */
> if (user_mode(regs))
> return -EFAULT;
The "insn_ma" pointer is always the same as the 'ma' argument
you already pass, as both are set based on 'user_mode(regs)'.
Why not just use the pointer you already have?
Arnd
next prev parent reply other threads:[~2026-10-23 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 23:34 Florian Fuchs
2026-10-23 7:07 ` Arnd Bergmann [this message]
2026-10-23 7:15 ` Geert Uytterhoeven
2026-10-23 7:25 ` Arnd Bergmann
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=04cfcbc2-0021-4ba2-b3bf-0da3cc82d046@app.fastmail.com \
--to=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=fuchsfl@gmail.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=yoshinori.sato@nifty.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®