From: syzbot <syzbot+5ef4c078ccd6970db1b6@syzkaller.appspotmail.com>
To: bfoster@redhat.com, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] INFO: task hung in bch2_btree_node_update_key (2)
Date: Wed, 05 Feb 2025 00:52:04 -0800 [thread overview]
Message-ID: <67a326b4.050a0220.50516.0013.GAE@google.com> (raw)
In-Reply-To: <677b4e8d.050a0220.380ff0.0022.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 66951e4860d3c688bfa550ea4a19635b57e00eca
Author: Peter Zijlstra <peterz@infradead.org>
Date: Mon Jan 13 12:50:11 2025 +0000
sched/fair: Fix update_cfs_group() vs DELAY_DEQUEUE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11336318580000
start commit: 56e6a3499e14 Merge tag 'trace-v6.13-rc5' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ba7cde9482d6bb6
dashboard link: https://syzkaller.appspot.com/bug?extid=5ef4c078ccd6970db1b6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144666c4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1244e8b0580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: sched/fair: Fix update_cfs_group() vs DELAY_DEQUEUE
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-02-05 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 3:31 [syzbot] [bcachefs?] INFO: task hung in bch2_btree_node_update_key (2) syzbot
2025-02-05 8:52 ` 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 \
--in-reply-to=67a326b4.050a0220.50516.0013.GAE@google.com \
--to=syzbot+5ef4c078ccd6970db1b6@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox