From: syzbot <syzbot+1fa48dc6faf1ff972d7d@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,
yohan.joung@sk.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in build_sit_entries
Date: Mon, 26 May 2025 10:42:01 -0700 [thread overview]
Message-ID: <6834a7e9.a70a0220.29d4a0.0807.GAE@google.com> (raw)
In-Reply-To: <68345c8d.a70a0220.253bc2.0097.GAE@google.com>
syzbot has bisected this issue to:
commit 313d10d79a82358bd8c3ee7ecda6356b1f7cde55
Author: yohan.joung <yohan.joung@sk.com>
Date: Mon May 12 07:36:10 2025 +0000
f2fs: add ckpt_valid_blocks to the section entry
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1300d170580000
start commit: 176e917e010c Add linux-next specific files for 20250523
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1080d170580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1700d170580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e7902c752bef748
dashboard link: https://syzkaller.appspot.com/bug?extid=1fa48dc6faf1ff972d7d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128bead4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=100288e8580000
Reported-by: syzbot+1fa48dc6faf1ff972d7d@syzkaller.appspotmail.com
Fixes: 313d10d79a82 ("f2fs: add ckpt_valid_blocks to the section entry")
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
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+1fa48dc6faf1ff972d7d@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,
yohan.joung@sk.com
Subject: Re: [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in build_sit_entries
Date: Mon, 26 May 2025 10:42:01 -0700 [thread overview]
Message-ID: <6834a7e9.a70a0220.29d4a0.0807.GAE@google.com> (raw)
In-Reply-To: <68345c8d.a70a0220.253bc2.0097.GAE@google.com>
syzbot has bisected this issue to:
commit 313d10d79a82358bd8c3ee7ecda6356b1f7cde55
Author: yohan.joung <yohan.joung@sk.com>
Date: Mon May 12 07:36:10 2025 +0000
f2fs: add ckpt_valid_blocks to the section entry
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1300d170580000
start commit: 176e917e010c Add linux-next specific files for 20250523
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1080d170580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1700d170580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e7902c752bef748
dashboard link: https://syzkaller.appspot.com/bug?extid=1fa48dc6faf1ff972d7d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128bead4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=100288e8580000
Reported-by: syzbot+1fa48dc6faf1ff972d7d@syzkaller.appspotmail.com
Fixes: 313d10d79a82 ("f2fs: add ckpt_valid_blocks to the section entry")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-05-26 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 12:20 [f2fs-dev] [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in build_sit_entries syzbot
2025-05-26 12:20 ` syzbot
2025-05-26 17:42 ` syzbot [this message]
2025-05-26 17:42 ` syzbot
2025-05-28 7:28 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-05-28 7:28 ` Chao Yu
2025-05-28 8:04 ` [f2fs-dev] " syzbot
2025-05-28 8:04 ` syzbot
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=6834a7e9.a70a0220.29d4a0.0807.GAE@google.com \
--to=syzbot+1fa48dc6faf1ff972d7d@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 \
--cc=yohan.joung@sk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.