From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, zong.li@sifive.com,
linux-kernel@vger.kernel.org,
syzbot+2c2a76232878c44e0eae@syzkaller.appspotmail.com
Subject: Re: [PATCH -fixes] riscv: Check if the code to patch lies in the exit section
Date: Fri, 08 Dec 2023 16:10:24 +0000 [thread overview]
Message-ID: <170205182486.7426.12012524229624787875.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231206165458.40610-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 6 Dec 2023 17:54:58 +0100 you wrote:
> Otherwise we fall through to vmalloc_to_page() which panics since the
> address does not lie in the vmalloc region.
>
> Fixes: 043cb41a85de ("riscv: introduce interfaces to patch kernel code")
> Reported-by: syzbot+2c2a76232878c44e0eae@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/all/000000000000ce4a27060b39ed34@google.com/T/
> Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
>
> [...]
Here is the summary with links:
- [-fixes] riscv: Check if the code to patch lies in the exit section
https://git.kernel.org/riscv/c/eb46a0076501
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:[~2023-12-08 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 16:54 Alexandre Ghiti
2023-12-08 16:10 ` 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=170205182486.7426.12012524229624787875.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--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=syzbot+2c2a76232878c44e0eae@syzkaller.appspotmail.com \
--cc=zong.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®