From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, Viktor Malik <vmalik@redhat.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@ozlabs.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, Saket Kumar Bhaskar <skb99@linux.ibm.com>
Subject: Re: [PATCH v2] powerpc, perf: Check that current->mm is alive before getting user callchain
Date: Sun, 15 Mar 2026 09:31:45 +0530 [thread overview]
Message-ID: <177354720780.2367911.1351341217164691365.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260309144045.169427-1-vmalik@redhat.com>
On Mon, 09 Mar 2026 15:40:45 +0100, Viktor Malik wrote:
> It may happen that mm is already released, which leads to kernel panic.
> This adds the NULL check for current->mm, similarly to 20afc60f892d
> ("x86, perf: Check that current->mm is alive before getting user
> callchain").
>
> I was getting this panic when running a profiling BPF program
> (profile.py from bcc-tools):
>
> [...]
Applied to powerpc/fixes.
[1/1] powerpc, perf: Check that current->mm is alive before getting user callchain
https://git.kernel.org/powerpc/c/e9bbfb4bfa86c6b5515b868d6982ac60505d7e39
cheers
prev parent reply other threads:[~2026-03-15 4:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 14:40 [PATCH v2] powerpc, perf: Check that current->mm is alive before getting user callchain Viktor Malik
2026-03-09 16:29 ` Saket Kumar Bhaskar
2026-03-10 6:30 ` Venkat
2026-03-10 13:24 ` Qiao Zhao
2026-03-15 4:01 ` Madhavan Srinivasan [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=177354720780.2367911.1351341217164691365.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bpf@vger.kernel.org \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@ozlabs.org \
--cc=skb99@linux.ibm.com \
--cc=vmalik@redhat.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