From: patchwork-bot+linux-riscv@kernel.org
To: Liao Chang <liaochang1@huawei.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, mhiramat@kernel.org,
guoren@kernel.org, me@packi.ch, penberg@kernel.org,
linux-kernel@vger.kernel.org, bjorn@kernel.org,
chenlifu@huawei.com
Subject: Re: [PATCH] riscv/kprobe: Fix instruction simulation of JALR
Date: Wed, 25 Jan 2023 05:50:16 +0000 [thread overview]
Message-ID: <167462581691.3015.5045414056306333462.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230116064342.2092136-1-liaochang1@huawei.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 16 Jan 2023 14:43:42 +0800 you wrote:
> Set kprobe at 'jalr 1140(ra)' of vfs_write results in the following
> crash:
>
> [ 32.092235] Unable to handle kernel access to user memory without uaccess routines at virtual address 00aaaaaad77b1170
> [ 32.093115] Oops [#1]
> [ 32.093251] Modules linked in:
> [ 32.093626] CPU: 0 PID: 135 Comm: ftracetest Not tainted 6.2.0-rc2-00013-gb0aa5e5df0cb-dirty #16
> [ 32.093985] Hardware name: riscv-virtio,qemu (DT)
> [ 32.094280] epc : ksys_read+0x88/0xd6
> [ 32.094855] ra : ksys_read+0xc0/0xd6
> [ 32.095016] epc : ffffffff801cda80 ra : ffffffff801cdab8 sp : ff20000000d7bdc0
> [ 32.095227] gp : ffffffff80f14000 tp : ff60000080f9cb40 t0 : ffffffff80f13e80
> [ 32.095500] t1 : ffffffff8000c29c t2 : ffffffff800dbc54 s0 : ff20000000d7be60
> [ 32.095716] s1 : 0000000000000000 a0 : ffffffff805a64ae a1 : ffffffff80a83708
> [ 32.095921] a2 : ffffffff80f160a0 a3 : 0000000000000000 a4 : f229b0afdb165300
> [ 32.096171] a5 : f229b0afdb165300 a6 : ffffffff80eeebd0 a7 : 00000000000003ff
> [ 32.096411] s2 : ff6000007ff76800 s3 : fffffffffffffff7 s4 : 00aaaaaad77b1170
> [ 32.096638] s5 : ffffffff80f160a0 s6 : ff6000007ff76800 s7 : 0000000000000030
> [ 32.096865] s8 : 00ffffffc3d97be0 s9 : 0000000000000007 s10: 00aaaaaad77c9410
> [ 32.097092] s11: 0000000000000000 t3 : ffffffff80f13e48 t4 : ffffffff8000c29c
> [ 32.097317] t5 : ffffffff8000c29c t6 : ffffffff800dbc54
> [ 32.097505] status: 0000000200000120 badaddr: 00aaaaaad77b1170 cause: 000000000000000d
> [ 32.098011] [<ffffffff801cdb72>] ksys_write+0x6c/0xd6
> [ 32.098222] [<ffffffff801cdc06>] sys_write+0x2a/0x38
> [ 32.098405] [<ffffffff80003c76>] ret_from_syscall+0x0/0x2
>
> [...]
Here is the summary with links:
- riscv/kprobe: Fix instruction simulation of JALR
https://git.kernel.org/riscv/c/ca0254998be4
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-01-25 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 6:43 [PATCH] riscv/kprobe: Fix instruction simulation of JALR Liao Chang
2023-01-21 2:59 ` Guo Ren
2023-01-25 5:48 ` Palmer Dabbelt
2023-01-25 5:50 ` 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=167462581691.3015.5045414056306333462.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=chenlifu@huawei.com \
--cc=guoren@kernel.org \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=me@packi.ch \
--cc=mhiramat@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=penberg@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