From: Peter Zijlstra <peterz@infradead.org>
To: Pengfei Xu <pengfei.xu@intel.com>
Cc: peter.zijlstra@intel.com, linux-kernel@vger.kernel.org,
heng.su@intel.com
Subject: Re: [Syzkaller & bisect] There is "__perf_event_overflow" WARNING in v6.1-rc5 kernel in guest
Date: Wed, 16 Nov 2022 15:40:24 +0100 [thread overview]
Message-ID: <Y3T2WAzyJTZnDl8m@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <Y3RbiRmAKrDlVCxC@xpf.sh.intel.com>
On Wed, Nov 16, 2022 at 11:39:53AM +0800, Pengfei Xu wrote:
> Hi Peter and perf expert,
>
> Greeting!
>
> Platform: TGL-H
>
> There is "__perf_event_overflow" WARNING issue in v6.1-rc5 kernel in
> guest in double check test.
>
> Found first bad commit is ca6c21327c6af02b7eec31ce4b9a740a18c6c13f
> "perf: Fix missing SIGTRAPs"
>
> And revert this commit on top of v6.1-rc5, this issue could not be reproduced.
>
> Guest kconfig, reproduce code from syzkaller, and bisect info are in attached.
>
> And more detailed info is in link:
> https://github.com/xupengfe/syzkaller_logs/tree/main/221114_134736___perf_event_overflow
>
> If it's helpful and in time, please add the Reported-by tag from me.
Does this help?
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=perf/urgent&id=bb88f9695460bec25aa30ba9072595025cf6c8af
next prev parent reply other threads:[~2022-11-16 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 3:39 Pengfei Xu
2022-11-16 3:45 ` Pengfei Xu
2022-11-16 14:40 ` Peter Zijlstra [this message]
2022-11-17 1:37 ` Pengfei Xu
2022-11-17 18:11 ` Peter Zijlstra
2022-11-19 2:45 ` Pengfei Xu
2022-11-23 15:05 ` Peter Zijlstra
2022-11-23 15:06 ` Peter Zijlstra
2022-11-23 15:26 ` Pengfei Xu
2022-11-24 1:40 ` Pengfei Xu
2022-11-24 8:31 ` Marco Elver
2022-11-24 9:00 ` Peter Zijlstra
2022-11-24 10:34 ` Peter Zijlstra
2022-11-24 9:43 ` [tip: perf/urgent] perf: Consider OS filter fail 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=Y3T2WAzyJTZnDl8m@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=heng.su@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pengfei.xu@intel.com \
--cc=peter.zijlstra@intel.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
all inboxes | Powered by JetHome®