From: syzbot <syzbot+5c81eb8c0a380fa578b5@syzkaller.appspotmail.com>
To: chao@kernel.org, drosen@google.com, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] kernel BUG in f2fs_evict_inode (4)
Date: Sat, 07 Dec 2024 14:59:02 -0800 [thread overview]
Message-ID: <6754d336.050a0220.2477f.0021.GAE@google.com> (raw)
In-Reply-To: <67388dcc.050a0220.bb738.0008.GAE@google.com>
syzbot has bisected this issue to:
commit acff9409dd40beaca2bd982678d222e2740ad84b
Author: Jaegeuk Kim <jaegeuk@kernel.org>
Date: Tue Nov 12 01:04:58 2024 +0000
Revert "f2fs: remove unreachable lazytime mount option parsing"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=130903e8580000
start commit: b8f52214c61a Merge tag 'audit-pr-20241205' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=108903e8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=170903e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=335e39020523e2ed
dashboard link: https://syzkaller.appspot.com/bug?extid=5c81eb8c0a380fa578b5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155bd0f8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13cad330580000
Reported-by: syzbot+5c81eb8c0a380fa578b5@syzkaller.appspotmail.com
Fixes: acff9409dd40 ("Revert "f2fs: remove unreachable lazytime mount option parsing"")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-12-07 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 12:19 [syzbot] [f2fs?] kernel BUG in f2fs_evict_inode (4) syzbot
2024-12-06 17:07 ` syzbot
2024-12-07 22:59 ` 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=6754d336.050a0220.2477f.0021.GAE@google.com \
--to=syzbot+5c81eb8c0a380fa578b5@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=drosen@google.com \
--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