From: hlsong <pgeorge8929@gmail.com>
To: Guo Ren <guoren@kernel.org>
Cc: linux-csky@vger.kernel.org, linux-kernel@vger.kernel.org,
hlsong89 <pgeorge8929@gmail.com>
Subject: [PATCH] csky: Fix a4/a5 restoration in syscall trace path
Date: Thu, 21 May 2026 17:59:46 +0800 [thread overview]
Message-ID: <20260521095946.37876-1-pgeorge8929@gmail.com> (raw)
From: hlsong89 <pgeorge8929@gmail.com>
The syscall trace path reloads syscall arguments from pt_regs before
calling the syscall handler. On C-SKY ABIv2, the 5th and 6th syscall
arguments are prepared as stack arguments before invoking syscallid.
The current code adjusts sp before loading LSAVE_A4 and LSAVE_A5. Since
those offsets are relative to the original pt_regs base, loading them
after changing sp fetches the wrong slots. As a result, traced syscalls
that use the 5th or 6th argument may receive corrupted arguments.
This is visible with mmap2(), which takes six arguments. A small
PTRACE_SYSCALL reproducer opens a file and maps one page with:
mmap(NULL, 4096, PROT_READ | PROT_EXEC, MAP_PRIVATE, fd, 0)
Before the fix, the traced child fails the mmap and exits with 12.
After the fix, the mapping succeeds and the child exits with 0.
Fix the trace path by using the correct pt_regs offsets after adjusting sp.
Tested on: ck860f, linux-4.19.15, C-SKY abiv2
Signed-off-by: hlsong89 <pgeorge8929@gmail.com>
---
arch/csky/kernel/entry.S | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/csky/kernel/entry.S b/arch/csky/kernel/entry.S
index c68cdcc76..98692fc78 100644
--- a/arch/csky/kernel/entry.S
+++ b/arch/csky/kernel/entry.S
@@ -94,9 +94,9 @@ csky_syscall_trace:
ldw a3, (sp, LSAVE_A3)
#if defined(__CSKYABIV2__)
subi sp, 8
- ldw r9, (sp, LSAVE_A4)
+ ldw r9, (sp, LSAVE_A4 + 8)
stw r9, (sp, 0x0)
- ldw r9, (sp, LSAVE_A5)
+ ldw r9, (sp, LSAVE_A5 + 8)
stw r9, (sp, 0x4)
jsr syscallid /* Do system call */
addi sp, 8
--
2.25.1
next reply other threads:[~2026-05-21 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 9:59 hlsong [this message]
2026-05-21 10:15 ` [PATCH] csky: Fix a4/a5 restoration in syscall trace path Guo Ren
2026-05-21 11:33 ` [PATCH v2] " hlsong
2026-05-21 15:44 ` Guo Ren
2026-05-21 10:29 ` Hanlin Song
[not found] ` <CABvmTk2+kd9n7xwSK=nnDBK4nC62sS7Du-MVeY17XV-p9pRufQ@mail.gmail.com>
2026-05-22 0:53 ` Guo Ren
2026-05-22 3:18 ` [PATCH v3] " Hanlin Song
2026-06-04 3:59 ` Hanlin Song
2026-06-04 11:44 ` Guo Ren
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=20260521095946.37876-1-pgeorge8929@gmail.com \
--to=pgeorge8929@gmail.com \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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