From: Peter Zijlstra <peterz@infradead.org>
To: James Clark <james.clark@linaro.org>
Cc: Oliver Sang <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
Ravi Bangoria <ravi.bangoria@amd.com>,
linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [tip:perf/core] [perf] da916e96e2: BUG:KASAN:null-ptr-deref_in_put_event
Date: Tue, 15 Apr 2025 12:08:40 +0200 [thread overview]
Message-ID: <20250415100840.GM5600@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <5bc5f54b-ce6a-4834-86d4-5014d44c7217@linaro.org>
On Tue, Apr 15, 2025 at 10:14:05AM +0100, James Clark wrote:
> On 15/04/2025 5:46 am, Oliver Sang wrote:
> > yes, below patch fixes the issues we observed for da916e96e2. thanks
> >
> > Tested-by: kernel test robot <oliver.sang@intel.com>
> >
>
> Also fixes the same issues we were seeing:
>
> Tested-by: James Clark <james.clark@linaro.org>
Excellent, thank you both! Now I gotta go write me a Changelog :-)
next prev parent reply other threads:[~2025-04-15 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 1:59 [tip:perf/core] [perf] da916e96e2: BUG:KASAN:null-ptr-deref_in_put_event kernel test robot
2025-04-14 19:01 ` Peter Zijlstra
2025-04-15 4:46 ` Oliver Sang
2025-04-15 9:14 ` James Clark
2025-04-15 10:08 ` Peter Zijlstra [this message]
2025-04-15 13:14 ` Peter Zijlstra
2025-04-15 15:52 ` James Clark
2025-04-16 8:46 ` Peter Zijlstra
2025-04-16 19:08 ` Peter Zijlstra
2025-04-17 8:58 ` James Clark
2025-04-16 8:36 ` Venkat Rao Bagalkote
2025-04-17 13:01 ` [tip: perf/core] perf/core: Fix event->parent life-time issue tip-bot2 for Peter Zijlstra
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=20250415100840.GM5600@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=james.clark@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=ravi.bangoria@amd.com \
--cc=x86@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 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.