From: patchwork-bot+linux-riscv@kernel.org
To: Stefan O'Rear <sorear@fastmail.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: process: Fix kernel gp leakage
Date: Thu, 04 Apr 2024 22:20:32 +0000 [thread overview]
Message-ID: <171226923206.6067.4805872086419688742.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240327061258.2370291-1-sorear@fastmail.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 27 Mar 2024 02:12:58 -0400 you wrote:
> childregs represents the registers which are active for the new thread
> in user context. For a kernel thread, childregs->gp is never used since
> the kernel gp is not touched by switch_to. For a user mode helper, the
> gp value can be observed in user space after execve or possibly by other
> means.
>
> Fixes: 7db91e57a0ac ("RISC-V: Task implementation")
> Signed-off-by: Stefan O'Rear <sorear@fastmail.com>
>
> [...]
Here is the summary with links:
- riscv: process: Fix kernel gp leakage
https://git.kernel.org/riscv/c/d14fa1fcf69d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-04 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 6:12 [PATCH] riscv: process: Fix kernel gp leakage Stefan O'Rear
2024-03-27 8:43 ` [External] " yunhui cui
2024-03-27 16:53 ` Stefan O'Rear
2024-03-28 12:09 ` yunhui cui
2024-04-02 9:21 ` Alexandre Ghiti
2024-04-04 20:13 ` Palmer Dabbelt
2024-04-04 22:20 ` patchwork-bot+linux-riscv [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=171226923206.6067.4805872086419688742.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=sorear@fastmail.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