From: syzbot <[email protected]>
To: [email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: Re: [syzbot] [kernel] WARNING: locking bug in sched_core_balance
Date: Thu, 02 Jan 2025 04:15:02 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
syzbot has bisected this issue to:
commit 7908632f2927b65f7486ae6b67c24071666ba43f
Author: Maíra Canal <[email protected]>
Date: Thu Sep 14 10:19:02 2023 +0000
Revert "drm/vkms: Fix race-condition between the hrtimer and the atomic commit"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=111018b0580000
start commit: ccb98ccef0e5 Merge tag 'platform-drivers-x86-v6.13-4' of g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=131018b0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=151018b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1c541fa8af5c9cc7
dashboard link: https://syzkaller.appspot.com/bug?extid=14641d8d78cc029add8a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127f3818580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=172306c4580000
Reported-by: [email protected]
Fixes: 7908632f2927 ("Revert "drm/vkms: Fix race-condition between the hrtimer and the atomic commit"")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-01-02 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2024-12-25 6:53 ` [syzbot] [io-uring?] WARNING: locking bug in sched_core_balance syzbot
2024-12-28 20:33 ` Jens Axboe
2025-01-01 20:58 ` [syzbot] [kernel] " syzbot
2025-01-02 12:15 ` syzbot [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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