From: syzbot <syzbot+2fe61cb2a86066be6985@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
penguin-kernel@i-love.sakura.ne.jp, peterz@infradead.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [perf?] WARNING in perf_pending_task
Date: Sat, 05 Jul 2025 08:05:05 -0700 [thread overview]
Message-ID: <68693f21.a00a0220.c7b3.003e.GAE@google.com> (raw)
In-Reply-To: <f8dee957-d286-421d-976a-c0c580454fb3@I-love.SAKURA.ne.jp>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+2fe61cb2a86066be6985@syzkaller.appspotmail.com
Tested-by: syzbot+2fe61cb2a86066be6985@syzkaller.appspotmail.com
Tested on:
commit: a79a588f Merge tag 'pm-6.16-rc5' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13691c8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a6dba31fc9bb876c
dashboard link: https://syzkaller.appspot.com/bug?extid=2fe61cb2a86066be6985
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=157a2582580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-07-05 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 19:01 [syzbot] [perf?] WARNING in perf_pending_task syzbot
2025-06-29 10:51 ` Tetsuo Handa
2025-07-05 14:43 ` [PATCH] perf/core: Fix WARN in perf_sigtrap() Tetsuo Handa
2025-07-05 15:05 ` syzbot [this message]
2025-07-09 9:44 ` Peter Zijlstra
2025-07-09 10:47 ` Tetsuo Handa
2025-07-09 11:27 ` [PATCH v2] " Tetsuo Handa
2025-07-10 12:46 ` [tip: perf/urgent] " tip-bot2 for Tetsuo Handa
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=68693f21.a00a0220.c7b3.003e.GAE@google.com \
--to=syzbot+2fe61cb2a86066be6985@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.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 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.