All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Mathis Salmen <mathis.salmen@matsal.de>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com
Subject: Re: [PATCH v2] riscv: add icache flush for nommu sigreturn trampoline
Date: Tue, 11 Apr 2023 20:00:17 +0000	[thread overview]
Message-ID: <168124321768.4909.15241149293858055772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230406101130.82304-1-mathis.salmen@matsal.de>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Thu,  6 Apr 2023 12:11:31 +0200 you wrote:
> In a NOMMU kernel, sigreturn trampolines are generated on the user
> stack by setup_rt_frame. Currently, these trampolines are not instruction
> fenced, thus their visibility to ifetch is not guaranteed.
> 
> This patch adds a flush_icache_range in setup_rt_frame to fix this
> problem.
> 
> [...]

Here is the summary with links:
  - [v2] riscv: add icache flush for nommu sigreturn trampoline
    https://git.kernel.org/riscv/c/8d736482749f

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

      parent reply	other threads:[~2023-04-11 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 10:11 [PATCH v2] riscv: add icache flush for nommu sigreturn trampoline Mathis Salmen
2023-04-08 19:51 ` Conor Dooley
2023-04-11 19:52 ` Palmer Dabbelt
2023-04-11 20:00 ` 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=168124321768.4909.15241149293858055772.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mathis.salmen@matsal.de \
    --cc=palmer@dabbelt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.