From: syzbot <syzbot+f4649be1be739e030111@syzkaller.appspotmail.com>
To: chao@kernel.org, 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: [syzbot] [f2fs?] general protection fault in f2fs_drop_extent_tree
Date: Tue, 01 Aug 2023 17:41:28 -0700 [thread overview]
Message-ID: <00000000000099695a0601e5ecfb@google.com> (raw)
In-Reply-To: <000000000000af3d3105ff38ee3c@google.com>
syzbot suspects this issue was fixed by commit:
commit 458c15dfbce62c35fefd9ca637b20a051309c9f1
Author: Chao Yu <chao@kernel.org>
Date: Tue May 23 03:58:22 2023 +0000
f2fs: don't reset unchangable mount option in f2fs_remount()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12461d31a80000
start commit: a92b7d26c743 Merge tag 'drm-fixes-2023-06-23' of git://ano..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2cbd298d0aff1140
dashboard link: https://syzkaller.appspot.com/bug?extid=f4649be1be739e030111
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1564afb0a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166928c7280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: f2fs: don't reset unchangable mount option in f2fs_remount()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-02 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 23:27 [syzbot] [f2fs?] general protection fault in f2fs_drop_extent_tree syzbot
2023-08-02 0:41 ` syzbot [this message]
2023-08-02 14:26 ` Aleksandr Nogikh
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=00000000000099695a0601e5ecfb@google.com \
--to=syzbot+f4649be1be739e030111@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--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).