From: patchwork-bot+linux-riscv@kernel.org
To: Andrew Jones <ajones@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, evan@rivosinc.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, conor.dooley@microchip.com,
apatel@ventanamicro.com
Subject: Re: [PATCH] RISC-V: hwprobe: Fix vDSO SIGSEGV
Date: Thu, 02 Nov 2023 20:20:30 +0000 [thread overview]
Message-ID: <169895643048.22248.514127597835305748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231010165101.14942-2-ajones@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 10 Oct 2023 18:51:02 +0200 you wrote:
> A hwprobe pair key is signed, but the hwprobe vDSO function was
> only checking that the upper bound was valid. In order to help
> avoid this type of problem in the future, and in anticipation of
> this check becoming more complicated with sparse keys, introduce
> and use a "key is valid" predicate function for the check.
>
> Fixes: aa5af0aa90ba ("RISC-V: Add hwprobe vDSO function and data")
> Signed-off-by: Andrew Jones <ajones@ventanamicro.com>
>
> [...]
Here is the summary with links:
- RISC-V: hwprobe: Fix vDSO SIGSEGV
https://git.kernel.org/riscv/c/899376e85ae5
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
prev parent reply other threads:[~2023-11-02 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 16:51 [PATCH] RISC-V: hwprobe: Fix vDSO SIGSEGV Andrew Jones
2023-10-10 18:16 ` Evan Green
2023-11-02 20: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=169895643048.22248.514127597835305748.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=conor.dooley@microchip.com \
--cc=evan@rivosinc.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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.