From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
netdev@vger.kernel.org, bjorn@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
song@kernel.org, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, palmer@dabbelt.com, luke.r.nels@gmail.com,
pulehui@huawei.com
Subject: Re: [PATCH bpf] riscv, bpf: Fix unpredictable kernel crash about RV64 struct_ops
Date: Tue, 23 Jan 2024 22:41:21 +0000 [thread overview]
Message-ID: <170604968128.538.9171637206468068779.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240123023207.1917284-1-pulehui@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 23 Jan 2024 02:32:07 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> We encountered a kernel crash triggered by the bpf_tcp_ca testcase as
> show below:
>
> Unable to handle kernel paging request at virtual address ff60000088554500
> Oops [#1]
> ...
> CPU: 3 PID: 458 Comm: test_progs Tainted: G OE 6.8.0-rc1-kselftest_plain #1
> Hardware name: riscv-virtio,qemu (DT)
> epc : 0xff60000088554500
> ra : tcp_ack+0x288/0x1232
> epc : ff60000088554500 ra : ffffffff80cc7166 sp : ff2000000117ba50
> gp : ffffffff82587b60 tp : ff60000087be0040 t0 : ff60000088554500
> t1 : ffffffff801ed24e t2 : 0000000000000000 s0 : ff2000000117bbc0
> s1 : 0000000000000500 a0 : ff20000000691000 a1 : 0000000000000018
> a2 : 0000000000000001 a3 : ff60000087be03a0 a4 : 0000000000000000
> a5 : 0000000000000000 a6 : 0000000000000021 a7 : ffffffff8263f880
> s2 : 000000004ac3c13b s3 : 000000004ac3c13a s4 : 0000000000008200
> s5 : 0000000000000001 s6 : 0000000000000104 s7 : ff2000000117bb00
> s8 : ff600000885544c0 s9 : 0000000000000000 s10: ff60000086ff0b80
> s11: 000055557983a9c0 t3 : 0000000000000000 t4 : 000000000000ffc4
> t5 : ffffffff8154f170 t6 : 0000000000000030
> status: 0000000200000120 badaddr: ff60000088554500 cause: 000000000000000c
> Code: c796 67d7 0000 0000 0052 0002 c13b 4ac3 0000 0000 (0001) 0000
>
> [...]
Here is the summary with links:
- [bpf] riscv, bpf: Fix unpredictable kernel crash about RV64 struct_ops
https://git.kernel.org/bpf/bpf/c/1732ebc4a261
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:[~2024-01-23 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 2:32 [PATCH bpf] riscv, bpf: Fix unpredictable kernel crash about RV64 struct_ops Pu Lehui
2024-01-23 22:41 ` patchwork-bot+netdevbpf [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=170604968128.538.9171637206468068779.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.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