From: syzbot <syzbot+e5b81eaab292e00e7d98@syzkaller.appspotmail.com>
To: chao@kernel.org, hdanton@sina.com, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_release_file
Date: Fri, 29 Sep 2023 19:42:30 -0700 [thread overview]
Message-ID: <000000000000178f6f06068a7e9a@google.com> (raw)
In-Reply-To: <000000000000cbb5f505faa4d920@google.com>
syzbot suspects this issue was fixed by commit:
commit 5079e1c0c879311668b77075de3e701869804adf
Author: Chao Yu <chao@kernel.org>
Date: Fri Jun 2 08:36:05 2023 +0000
f2fs: avoid dead loop in f2fs_issue_checkpoint()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f18a92680000
start commit: b6dad5178cea Merge tag 'nios2_fix_v6.4' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ac246111fb601aec
dashboard link: https://syzkaller.appspot.com/bug?extid=e5b81eaab292e00e7d98
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c50e17280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a9558b280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: f2fs: avoid dead loop in f2fs_issue_checkpoint()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-09-30 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 17:06 [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_release_file syzbot
2023-06-15 8:39 ` syzbot
2023-09-30 2:42 ` 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=000000000000178f6f06068a7e9a@google.com \
--to=syzbot+e5b81eaab292e00e7d98@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=hdanton@sina.com \
--cc=jaegeuk@kernel.org \
--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).