From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, atishp@atishpatra.org,
anup@brainfault.org, will@kernel.org, mark.rutland@arm.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, ajones@ventanamicro.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -fixes] drivers: perf: Fix panic in riscv SBI mmap support
Date: Thu, 12 Oct 2023 20:40:25 +0000 [thread overview]
Message-ID: <169714322520.23371.17105611293776534650.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231006082010.11963-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 6 Oct 2023 10:20:10 +0200 you wrote:
> The following panic can happen when mmap is called before the pmu add
> callback which sets the hardware counter index: this happens for example
> with the following command `perf record --no-bpf-event -n kill`.
>
> [ 99.461486] CPU: 1 PID: 1259 Comm: perf Tainted: G E 6.6.0-rc4ubuntu-defconfig #2
> [ 99.461669] Hardware name: riscv-virtio,qemu (DT)
> [ 99.461748] epc : pmu_sbi_set_scounteren+0x42/0x44
> [ 99.462337] ra : smp_call_function_many_cond+0x126/0x5b0
> [ 99.462369] epc : ffffffff809f9d24 ra : ffffffff800f93e0 sp : ff60000082153aa0
> [ 99.462407] gp : ffffffff82395c98 tp : ff6000009a218040 t0 : ff6000009ab3a4f0
> [ 99.462425] t1 : 0000000000000004 t2 : 0000000000000100 s0 : ff60000082153ab0
> [ 99.462459] s1 : 0000000000000000 a0 : ff60000098869528 a1 : 0000000000000000
> [ 99.462473] a2 : 000000000000001f a3 : 0000000000f00000 a4 : fffffffffffffff8
> [ 99.462488] a5 : 00000000000000cc a6 : 0000000000000000 a7 : 0000000000735049
> [ 99.462502] s2 : 0000000000000001 s3 : ffffffff809f9ce2 s4 : ff60000098869528
> [ 99.462516] s5 : 0000000000000002 s6 : 0000000000000004 s7 : 0000000000000001
> [ 99.462530] s8 : ff600003fec98bc0 s9 : ffffffff826c5890 s10: ff600003fecfcde0
> [ 99.462544] s11: ff600003fec98bc0 t3 : ffffffff819e2558 t4 : ff1c000004623840
> [ 99.462557] t5 : 0000000000000901 t6 : ff6000008feeb890
> [ 99.462570] status: 0000000200000100 badaddr: 0000000000000000 cause: 0000000000000003
> [ 99.462658] [<ffffffff809f9d24>] pmu_sbi_set_scounteren+0x42/0x44
> [ 99.462979] Code: 1060 4785 97bb 00d7 8fd9 9073 1067 6422 0141 8082 (9002) 0013
> [ 99.463335] Kernel BUG [#2]
>
> [...]
Here is the summary with links:
- [-fixes] drivers: perf: Fix panic in riscv SBI mmap support
https://git.kernel.org/riscv/c/3fec323339a4
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-10-12 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 8:20 [PATCH -fixes] drivers: perf: Fix panic in riscv SBI mmap support Alexandre Ghiti
2023-10-12 20:40 ` 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=169714322520.23371.17105611293776534650.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=will@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