From: syzbot <syzbot+8b85865808c8908a0d8c@syzkaller.appspotmail.com>
To: chao@kernel.org, hdanton@sina.com, jaegeuk@kernel.org,
jiayang5@huawei.com, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] INFO: task hung in f2fs_balance_fs
Date: Sun, 26 Mar 2023 09:58:23 -0700 [thread overview]
Message-ID: <000000000000c4832e05f7d088c6@google.com> (raw)
In-Reply-To: <0000000000000ac4cc05f6e7f12b@google.com>
syzbot has bisected this issue to:
commit 10d0786b39b3b91c4fbf8c2926e97ab456a4eea1
Author: Jia Yang <jiayang5@huawei.com>
Date: Wed Jul 14 07:46:06 2021 +0000
f2fs: Revert "f2fs: Fix indefinite loop in f2fs_gc() v1"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13426789c80000
start commit: 4bdec23f971b Merge tag 'hwmon-for-v6.3-rc4' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10c26789c80000
console output: https://syzkaller.appspot.com/x/log.txt?x=17426789c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea09b0836073ee4
dashboard link: https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1320ef41c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=100b561ec80000
Reported-by: syzbot+8b85865808c8908a0d8c@syzkaller.appspotmail.com
Fixes: 10d0786b39b3 ("f2fs: Revert "f2fs: Fix indefinite loop in f2fs_gc() v1"")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-03-26 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 3:28 [syzbot] [f2fs?] INFO: task hung in f2fs_balance_fs syzbot
2023-03-26 5:17 ` syzbot
2024-06-04 15:12 ` Chao Yu
2024-06-04 15:40 ` syzbot
2023-03-26 16:58 ` 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=000000000000c4832e05f7d088c6@google.com \
--to=syzbot+8b85865808c8908a0d8c@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=hdanton@sina.com \
--cc=jaegeuk@kernel.org \
--cc=jiayang5@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).