From: syzbot <syzbot+aac7bff85be224de5156@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, clm@fb.com, dsterba@suse.com,
fdmanana@kernel.org, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
nogikh@google.com, peterz@infradead.org, quwenruo.btrfs@gmx.com,
syzkaller-bugs@googlegroups.com, willy@infradead.org,
wqu@suse.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in __folio_start_writeback
Date: Wed, 22 Jan 2025 21:06:01 -0800 [thread overview]
Message-ID: <6791ce39.050a0220.194594.0020.GAE@google.com> (raw)
In-Reply-To: <67432dee.050a0220.1cc393.0041.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=11c129f8580000
start commit: 228a1157fb9f Merge tag '6.13-rc-part1-SMB3-client-fixes' o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=402159daa216c89d
dashboard link: https://syzkaller.appspot.com/bug?extid=aac7bff85be224de5156
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13840778580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17840778580000
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-01-23 5:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 13:45 syzbot
2024-11-24 21:26 ` Matthew Wilcox
2024-11-25 0:30 ` Qu Wenruo
2024-11-25 10:44 ` Aleksandr Nogikh
2024-11-26 8:43 ` Qu Wenruo
2024-11-26 6:42 ` Qu Wenruo
2024-11-26 7:35 ` syzbot
2024-11-28 18:56 ` syzbot
2024-11-28 21:26 ` Qu Wenruo
2024-11-29 21:17 ` Qu Wenruo
2024-11-30 1:51 ` syzbot
2024-11-30 4:27 ` Qu Wenruo
2024-11-30 6:36 ` Qu Wenruo
2024-11-30 7:01 ` syzbot
2025-01-23 5:06 ` 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=6791ce39.050a0220.194594.0020.GAE@google.com \
--to=syzbot+aac7bff85be224de5156@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nogikh@google.com \
--cc=peterz@infradead.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
--cc=wqu@suse.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