From: syzbot <syzbot+f195123a45ad487ca66c@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] kernel BUG in f2fs_vm_page_mkwrite
Date: Mon, 05 Aug 2024 08:22:03 -0700 [thread overview]
Message-ID: <00000000000038c729061ef13d67@google.com> (raw)
In-Reply-To: <0000000000004d2e4d061a401e51@google.com>
syzbot suspects this issue was fixed by commit:
commit a8eb3de28e7a365690c61161e7a07a4fc7c60bbf
Author: Chao Yu <chao@kernel.org>
Date: Mon Jun 3 01:07:45 2024 +0000
f2fs: fix return value of f2fs_convert_inline_inode()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1055414b980000
start commit: 83814698cf48 Merge tag 'powerpc-6.10-2' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=238430243a58f702
dashboard link: https://syzkaller.appspot.com/bug?extid=f195123a45ad487ca66c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1129d362980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d4ce06980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: f2fs: fix return value of f2fs_convert_inline_inode()
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
next prev parent reply other threads:[~2024-08-05 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 22:22 [f2fs-dev] [syzbot] [f2fs?] kernel BUG in f2fs_vm_page_mkwrite syzbot
2024-08-05 15:22 ` syzbot [this message]
2024-08-20 1:41 ` Chao Yu
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=00000000000038c729061ef13d67@google.com \
--to=syzbot+f195123a45ad487ca66c@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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).