From: Nathan Chancellor <nathan@kernel.org>
To: "Dmitry V. Levin" <ldv@strace.io>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
Charlie Jenkins <charlie@rivosinc.com>,
Arnd Bergmann <arnd@arndb.de>,
strace-devel@lists.strace.io, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v7 2/6] syscall.h: add syscall_set_arguments()
Date: Wed, 9 Apr 2025 08:52:07 -0700 [thread overview]
Message-ID: <20250409155207.GA1506425@ax162> (raw)
In-Reply-To: <20250409064017.GA30836@strace.io>
On Wed, Apr 09, 2025 at 09:40:18AM +0300, Dmitry V. Levin wrote:
> On Tue, Apr 08, 2025 at 05:38:03PM -0700, Nathan Chancellor wrote:
> > diff --git a/arch/riscv/include/asm/syscall.h b/arch/riscv/include/asm/syscall.h
> > index a5281cdf2b10..34313387f977 100644
> > --- a/arch/riscv/include/asm/syscall.h
> > +++ b/arch/riscv/include/asm/syscall.h
> > @@ -69,8 +69,11 @@ static inline void syscall_get_arguments(struct task_struct *task,
> > unsigned long *args)
> > {
> > args[0] = regs->orig_a0;
> > - args++;
> > - memcpy(args, ®s->a1, 5 * sizeof(args[0]));
> > + args[1] = regs->a1;
> > + args[2] = regs->a2;
> > + args[3] = regs->a3;
> > + args[4] = regs->a4;
> > + args[5] = regs->a5;
> > }
> >
> > static inline void syscall_set_arguments(struct task_struct *task,
> > @@ -78,8 +81,11 @@ static inline void syscall_set_arguments(struct task_struct *task,
> > const unsigned long *args)
> > {
> > regs->orig_a0 = args[0];
> > - args++;
> > - memcpy(®s->a1, args, 5 * sizeof(regs->a1));
> > + regs->a1 = args[1];
> > + regs->a2 = args[2];
> > + regs->a3 = args[3];
> > + regs->a4 = args[4];
> > + regs->a5 = args[5];
> > }
> >
> > static inline int syscall_get_arch(struct task_struct *task)
>
> Looks good, thanks. How do we proceed from this point?
I can send a standalone patch for syscall_get_arguments() since that is
an issue present before your series then Andrew could fold in the same
change for syscall_set_arguments() into your change that introduces it
so there is no bisect problem?
Cheers,
Nathan
next prev parent reply other threads:[~2025-04-09 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 11:19 [PATCH v7 0/6] ptrace: introduce PTRACE_SET_SYSCALL_INFO API Dmitry V. Levin
2025-03-03 11:19 ` [PATCH v7 1/6] hexagon: add syscall_set_return_value() Dmitry V. Levin
2025-03-03 11:20 ` [PATCH v7 2/6] syscall.h: add syscall_set_arguments() Dmitry V. Levin
2025-04-08 21:31 ` Nathan Chancellor
2025-04-08 22:36 ` Dmitry V. Levin
2025-04-09 0:38 ` Nathan Chancellor
2025-04-09 6:40 ` Dmitry V. Levin
2025-04-09 15:52 ` Nathan Chancellor [this message]
2025-04-09 23:18 ` Dmitry V. Levin
2025-04-10 18:14 ` Nathan Chancellor
2025-03-03 11:20 ` [PATCH v7 3/6] syscall.h: introduce syscall_set_nr() Dmitry V. Levin
2025-03-03 11:20 ` [PATCH v7 4/6] ptrace_get_syscall_info: factor out ptrace_get_syscall_info_op Dmitry V. Levin
2025-03-03 11:20 ` [PATCH v7 5/6] ptrace: introduce PTRACE_SET_SYSCALL_INFO request Dmitry V. Levin
2025-03-03 11:20 ` [PATCH v7 6/6] selftests/ptrace: add a test case for PTRACE_SET_SYSCALL_INFO Dmitry V. Levin
2025-03-06 2:02 ` [PATCH v7 0/6] ptrace: introduce PTRACE_SET_SYSCALL_INFO API Dmitry V. Levin
2025-03-25 10:41 ` Dmitry V. Levin
2025-03-25 17:57 ` Andrew Morton
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=20250409155207.GA1506425@ax162 \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=charlie@rivosinc.com \
--cc=ldv@strace.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oleg@redhat.com \
--cc=strace-devel@lists.strace.io \
/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