From: syzbot <syzbot+f24dd060c1911fe54c85@syzkaller.appspotmail.com>
To: andreyknvl@gmail.com, daniel.lezcano@linaro.org,
elver@google.com, jannh@google.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
lukasz.luba@arm.com, rafael@kernel.org, rui.zhang@intel.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [pm?] WARNING in thermal_thresholds_flush
Date: Fri, 18 Oct 2024 06:21:01 -0700 [thread overview]
Message-ID: <671260bd.050a0220.1e4b4d.0016.GAE@google.com> (raw)
In-Reply-To: <67124175.050a0220.10f4f4.0012.GAE@google.com>
syzbot has bisected this issue to:
commit b8c8ba73c68bb3c3e9dad22f488b86c540c839f9
Author: Jann Horn <jannh@google.com>
Date: Fri Aug 9 15:36:56 2024 +0000
slub: Introduce CONFIG_SLUB_RCU_DEBUG
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14cc4c5f980000
start commit: 15e7d45e786a Add linux-next specific files for 20241016
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12cc4c5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c36416f1c54640c0
dashboard link: https://syzkaller.appspot.com/bug?extid=f24dd060c1911fe54c85
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1192f887980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1417e830580000
Reported-by: syzbot+f24dd060c1911fe54c85@syzkaller.appspotmail.com
Fixes: b8c8ba73c68b ("slub: Introduce CONFIG_SLUB_RCU_DEBUG")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-18 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 11:07 [syzbot] [pm?] WARNING in thermal_thresholds_flush syzbot
2024-10-18 13:21 ` syzbot [this message]
2024-10-18 15:42 ` Jann Horn
2024-10-18 16:10 ` Aleksandr Nogikh
2024-10-21 8:19 ` Daniel Lezcano
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=671260bd.050a0220.1e4b4d.0016.GAE@google.com \
--to=syzbot+f24dd060c1911fe54c85@syzkaller.appspotmail.com \
--cc=andreyknvl@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=elver@google.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
/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