From: Qing Wang <wangqing7171@gmail.com>
To: andrii.nakryiko@gmail.com
Cc: acme@kernel.org, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, bpf@vger.kernel.org,
irogers@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mark.rutland@arm.com, mingo@redhat.com, namhyung@kernel.org,
peterz@infradead.org, radoslaw.zielonek@gmail.com,
syzbot+72a43cdb78469f7fbad1@syzkaller.appspotmail.com
Subject: Re: [PATCH] perf callchain: Fix suspicious RCU usage in get_callchain_entry()
Date: Wed, 28 Jan 2026 14:26:56 +0800 [thread overview]
Message-ID: <20260128062656.1860201-1-wangqing7171@gmail.com> (raw)
In-Reply-To: <CAEf4BzaYL9zZN8TZyRHW3_O3vbHc7On+NSunrkDvDQx2=wwyRw@mail.gmail.com>
On Fri, 19 Jul 2024 at 01:41, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
> Which is what I'm doing in [0]. Radoslaw, can you please help
> validating if those changes are enough to fix this issue or we need to
> do some more?
>
> [0] https://patchwork.kernel.org/project/netdevbpf/patch/20240709204245.3=
> 847811-10-andrii@kernel.org/
>
> >
> > > ---
> > > kernel/events/callchain.c | 11 +++++++++--
> > > 1 file changed, 9 insertions(+), 2 deletions(-)
> > >
Hi,
I found this issue still exists after your patch in upstream and I have a
patch to fix it.
Patch here: https://lore.kernel.org/all/20260128061753.1857803-1-wangqing7171@gmail.com/T/
Looking forward to your review.
--
Best regards,
Qing
next prev parent reply other threads:[~2026-01-28 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 10:23 [PATCH] perf callchain: Fix suspicious RCU usage in get_callchain_entry() Radoslaw Zielonek
2024-07-15 10:47 ` Peter Zijlstra
2024-07-18 17:41 ` Andrii Nakryiko
2026-01-28 6:26 ` Qing Wang [this message]
2026-01-28 8:19 ` Tao Chen
2026-01-28 8:45 ` Qing Wang
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=20260128062656.1860201-1-wangqing7171@gmail.com \
--to=wangqing7171@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=radoslaw.zielonek@gmail.com \
--cc=syzbot+72a43cdb78469f7fbad1@syzkaller.appspotmail.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