From: patchwork-bot+linux-riscv@kernel.org <patchwork-bot+linux-riscv@kernel.org>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH] RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
Date: Tue, 01 Oct 2024 11:35:21 +0000 [thread overview]
Message-ID: <172778252124.314421.2392376531840304330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240815170907.2792229-1-apatel@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Anup Patel <anup@brainfault.org>:
On Thu, 15 Aug 2024 22:39:07 +0530 you wrote:
> With the latest Linux-6.11-rc3, the below NULL pointer crash is observed
> when SBI PMU snapshot is enabled for the guest and the guest is forcefully
> powered-off.
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000508
> Oops [#1]
> Modules linked in: kvm
> CPU: 0 UID: 0 PID: 61 Comm: term-poll Not tainted 6.11.0-rc3-00018-g44d7178dd77a #3
> Hardware name: riscv-virtio,qemu (DT)
> epc : __kvm_write_guest_page+0x94/0xa6 [kvm]
> ra : __kvm_write_guest_page+0x54/0xa6 [kvm]
> epc : ffffffff01590e98 ra : ffffffff01590e58 sp : ffff8f80001f39b0
> gp : ffffffff81512a60 tp : ffffaf80024872c0 t0 : ffffaf800247e000
> t1 : 00000000000007e0 t2 : 0000000000000000 s0 : ffff8f80001f39f0
> s1 : 00007fff89ac4000 a0 : ffffffff015dd7e8 a1 : 0000000000000086
> a2 : 0000000000000000 a3 : ffffaf8000000000 a4 : ffffaf80024882c0
> a5 : 0000000000000000 a6 : ffffaf800328d780 a7 : 00000000000001cc
> s2 : ffffaf800197bd00 s3 : 00000000000828c4 s4 : ffffaf800248c000
> s5 : ffffaf800247d000 s6 : 0000000000001000 s7 : 0000000000001000
> s8 : 0000000000000000 s9 : 00007fff861fd500 s10: 0000000000000001
> s11: 0000000000800000 t3 : 00000000000004d3 t4 : 00000000000004d3
> t5 : ffffffff814126e0 t6 : ffffffff81412700
> status: 0000000200000120 badaddr: 0000000000000508 cause: 000000000000000d
> [<ffffffff01590e98>] __kvm_write_guest_page+0x94/0xa6 [kvm]
> [<ffffffff015943a6>] kvm_vcpu_write_guest+0x56/0x90 [kvm]
> [<ffffffff015a175c>] kvm_pmu_clear_snapshot_area+0x42/0x7e [kvm]
> [<ffffffff015a1972>] kvm_riscv_vcpu_pmu_deinit.part.0+0xe0/0x14e [kvm]
> [<ffffffff015a2ad0>] kvm_riscv_vcpu_pmu_deinit+0x1a/0x24 [kvm]
> [<ffffffff0159b344>] kvm_arch_vcpu_destroy+0x28/0x4c [kvm]
> [<ffffffff0158e420>] kvm_destroy_vcpus+0x5a/0xda [kvm]
> [<ffffffff0159930c>] kvm_arch_destroy_vm+0x14/0x28 [kvm]
> [<ffffffff01593260>] kvm_destroy_vm+0x168/0x2a0 [kvm]
> [<ffffffff015933d4>] kvm_put_kvm+0x3c/0x58 [kvm]
> [<ffffffff01593412>] kvm_vm_release+0x22/0x2e [kvm]
>
> [...]
Here is the summary with links:
- RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
https://git.kernel.org/riscv/c/47d40d93292d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, atishp@atishpatra.org,
ajones@ventanamicro.com, anup@brainfault.org,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
Date: Tue, 01 Oct 2024 11:35:21 +0000 [thread overview]
Message-ID: <172778252124.314421.2392376531840304330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240815170907.2792229-1-apatel@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Anup Patel <anup@brainfault.org>:
On Thu, 15 Aug 2024 22:39:07 +0530 you wrote:
> With the latest Linux-6.11-rc3, the below NULL pointer crash is observed
> when SBI PMU snapshot is enabled for the guest and the guest is forcefully
> powered-off.
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000508
> Oops [#1]
> Modules linked in: kvm
> CPU: 0 UID: 0 PID: 61 Comm: term-poll Not tainted 6.11.0-rc3-00018-g44d7178dd77a #3
> Hardware name: riscv-virtio,qemu (DT)
> epc : __kvm_write_guest_page+0x94/0xa6 [kvm]
> ra : __kvm_write_guest_page+0x54/0xa6 [kvm]
> epc : ffffffff01590e98 ra : ffffffff01590e58 sp : ffff8f80001f39b0
> gp : ffffffff81512a60 tp : ffffaf80024872c0 t0 : ffffaf800247e000
> t1 : 00000000000007e0 t2 : 0000000000000000 s0 : ffff8f80001f39f0
> s1 : 00007fff89ac4000 a0 : ffffffff015dd7e8 a1 : 0000000000000086
> a2 : 0000000000000000 a3 : ffffaf8000000000 a4 : ffffaf80024882c0
> a5 : 0000000000000000 a6 : ffffaf800328d780 a7 : 00000000000001cc
> s2 : ffffaf800197bd00 s3 : 00000000000828c4 s4 : ffffaf800248c000
> s5 : ffffaf800247d000 s6 : 0000000000001000 s7 : 0000000000001000
> s8 : 0000000000000000 s9 : 00007fff861fd500 s10: 0000000000000001
> s11: 0000000000800000 t3 : 00000000000004d3 t4 : 00000000000004d3
> t5 : ffffffff814126e0 t6 : ffffffff81412700
> status: 0000000200000120 badaddr: 0000000000000508 cause: 000000000000000d
> [<ffffffff01590e98>] __kvm_write_guest_page+0x94/0xa6 [kvm]
> [<ffffffff015943a6>] kvm_vcpu_write_guest+0x56/0x90 [kvm]
> [<ffffffff015a175c>] kvm_pmu_clear_snapshot_area+0x42/0x7e [kvm]
> [<ffffffff015a1972>] kvm_riscv_vcpu_pmu_deinit.part.0+0xe0/0x14e [kvm]
> [<ffffffff015a2ad0>] kvm_riscv_vcpu_pmu_deinit+0x1a/0x24 [kvm]
> [<ffffffff0159b344>] kvm_arch_vcpu_destroy+0x28/0x4c [kvm]
> [<ffffffff0158e420>] kvm_destroy_vcpus+0x5a/0xda [kvm]
> [<ffffffff0159930c>] kvm_arch_destroy_vm+0x14/0x28 [kvm]
> [<ffffffff01593260>] kvm_destroy_vm+0x168/0x2a0 [kvm]
> [<ffffffff015933d4>] kvm_put_kvm+0x3c/0x58 [kvm]
> [<ffffffff01593412>] kvm_vm_release+0x22/0x2e [kvm]
>
> [...]
Here is the summary with links:
- RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
https://git.kernel.org/riscv/c/47d40d93292d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, atishp@atishpatra.org,
ajones@ventanamicro.com, anup@brainfault.org,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
Date: Tue, 01 Oct 2024 11:35:21 +0000 [thread overview]
Message-ID: <172778252124.314421.2392376531840304330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240815170907.2792229-1-apatel@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Anup Patel <anup@brainfault.org>:
On Thu, 15 Aug 2024 22:39:07 +0530 you wrote:
> With the latest Linux-6.11-rc3, the below NULL pointer crash is observed
> when SBI PMU snapshot is enabled for the guest and the guest is forcefully
> powered-off.
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000508
> Oops [#1]
> Modules linked in: kvm
> CPU: 0 UID: 0 PID: 61 Comm: term-poll Not tainted 6.11.0-rc3-00018-g44d7178dd77a #3
> Hardware name: riscv-virtio,qemu (DT)
> epc : __kvm_write_guest_page+0x94/0xa6 [kvm]
> ra : __kvm_write_guest_page+0x54/0xa6 [kvm]
> epc : ffffffff01590e98 ra : ffffffff01590e58 sp : ffff8f80001f39b0
> gp : ffffffff81512a60 tp : ffffaf80024872c0 t0 : ffffaf800247e000
> t1 : 00000000000007e0 t2 : 0000000000000000 s0 : ffff8f80001f39f0
> s1 : 00007fff89ac4000 a0 : ffffffff015dd7e8 a1 : 0000000000000086
> a2 : 0000000000000000 a3 : ffffaf8000000000 a4 : ffffaf80024882c0
> a5 : 0000000000000000 a6 : ffffaf800328d780 a7 : 00000000000001cc
> s2 : ffffaf800197bd00 s3 : 00000000000828c4 s4 : ffffaf800248c000
> s5 : ffffaf800247d000 s6 : 0000000000001000 s7 : 0000000000001000
> s8 : 0000000000000000 s9 : 00007fff861fd500 s10: 0000000000000001
> s11: 0000000000800000 t3 : 00000000000004d3 t4 : 00000000000004d3
> t5 : ffffffff814126e0 t6 : ffffffff81412700
> status: 0000000200000120 badaddr: 0000000000000508 cause: 000000000000000d
> [<ffffffff01590e98>] __kvm_write_guest_page+0x94/0xa6 [kvm]
> [<ffffffff015943a6>] kvm_vcpu_write_guest+0x56/0x90 [kvm]
> [<ffffffff015a175c>] kvm_pmu_clear_snapshot_area+0x42/0x7e [kvm]
> [<ffffffff015a1972>] kvm_riscv_vcpu_pmu_deinit.part.0+0xe0/0x14e [kvm]
> [<ffffffff015a2ad0>] kvm_riscv_vcpu_pmu_deinit+0x1a/0x24 [kvm]
> [<ffffffff0159b344>] kvm_arch_vcpu_destroy+0x28/0x4c [kvm]
> [<ffffffff0158e420>] kvm_destroy_vcpus+0x5a/0xda [kvm]
> [<ffffffff0159930c>] kvm_arch_destroy_vm+0x14/0x28 [kvm]
> [<ffffffff01593260>] kvm_destroy_vm+0x168/0x2a0 [kvm]
> [<ffffffff015933d4>] kvm_put_kvm+0x3c/0x58 [kvm]
> [<ffffffff01593412>] kvm_vm_release+0x22/0x2e [kvm]
>
> [...]
Here is the summary with links:
- RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
https://git.kernel.org/riscv/c/47d40d93292d
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
next prev parent reply other threads:[~2024-10-01 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 17:09 [PATCH] RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data Anup Patel
2024-08-15 17:09 ` Anup Patel
2024-08-15 17:09 ` Anup Patel
2024-08-20 5:39 ` Anup Patel
2024-08-20 5:39 ` Anup Patel
2024-08-20 5:39 ` Anup Patel
2024-10-01 11:35 ` patchwork-bot+linux-riscv [this message]
2024-10-01 11:35 ` patchwork-bot+linux-riscv
2024-10-01 11:35 ` patchwork-bot+linux-riscv
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=172778252124.314421.2392376531840304330.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=kvm-riscv@lists.infradead.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 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.