From: patchwork-bot+linux-riscv@kernel.org
To: Celeste Liu <coelacanthushex@gmail.com>
Cc: linux-riscv@lists.infradead.org, bjorn@rivosinc.com,
linux-kernel@vger.kernel.org, ldv@strace.io, guoren@kernel.org,
palmer@rivosinc.com, emil.renner.berthing@canonical.com,
felixonmars@archlinux.org, c141028@gmail.com,
CoelacanthusHex@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] riscv: entry: always initialize regs->a0 to -ENOSYS
Date: Thu, 15 Aug 2024 17:50:35 +0000 [thread overview]
Message-ID: <172374423527.2967007.4867324910866661414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240627142338.5114-2-CoelacanthusHex@gmail.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 27 Jun 2024 22:23:39 +0800 you wrote:
> Otherwise when the tracer changes syscall number to -1, the kernel fails
> to initialize a0 with -ENOSYS and subsequently fails to return the error
> code of the failed syscall to userspace. For example, it will break
> strace syscall tampering.
>
> Fixes: 52449c17bdd1 ("riscv: entry: set a0 = -ENOSYS only when syscall != -1")
> Reported-by: "Dmitry V. Levin" <ldv@strace.io>
> Reviewed-by: Björn Töpel <bjorn@rivosinc.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Celeste Liu <CoelacanthusHex@gmail.com>
>
> [...]
Here is the summary with links:
- [v2] riscv: entry: always initialize regs->a0 to -ENOSYS
https://git.kernel.org/riscv/c/61119394631f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-08-15 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 14:23 [PATCH v2] riscv: entry: always initialize regs->a0 to -ENOSYS Celeste Liu
2024-08-15 17:50 ` patchwork-bot+linux-riscv [this message]
2024-09-16 16:49 ` Andrea Bolognani
2024-09-17 22:22 ` Dmitry V . Levin
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=172374423527.2967007.4867324910866661414.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=c141028@gmail.com \
--cc=coelacanthushex@gmail.com \
--cc=emil.renner.berthing@canonical.com \
--cc=felixonmars@archlinux.org \
--cc=guoren@kernel.org \
--cc=ldv@strace.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
--cc=stable@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