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
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in build_sit_entries
Date: Wed, 28 May 2025 01:04:01 -0700 [thread overview]
Message-ID: <6836c371.a70a0220.253bc2.00c4.GAE@google.com> (raw)
In-Reply-To: <68c2c045-c0d4-4896-b3e5-ba3d767f7110@kernel.org>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
Tested on:
commit: 8b56d4fb f2fs: fix to do sanity check on section ckpt_..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot
console output: https://syzkaller.appspot.com/x/log.txt?x=171403f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d25f4819d9920a3e
dashboard link: https://syzkaller.appspot.com/bug?extid=1fa48dc6faf1ff972d7d
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
Note: no patches were applied.
_______________________________________________
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
Subject: Re: [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in build_sit_entries
Date: Wed, 28 May 2025 01:04:01 -0700 [thread overview]
Message-ID: <6836c371.a70a0220.253bc2.00c4.GAE@google.com> (raw)
In-Reply-To: <68c2c045-c0d4-4896-b3e5-ba3d767f7110@kernel.org>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
Tested on:
commit: 8b56d4fb f2fs: fix to do sanity check on section ckpt_..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot
console output: https://syzkaller.appspot.com/x/log.txt?x=171403f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d25f4819d9920a3e
dashboard link: https://syzkaller.appspot.com/bug?extid=1fa48dc6faf1ff972d7d
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
Note: no patches were applied.
next prev parent reply other threads:[~2025-05-28 8:04 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 ` [f2fs-dev] " syzbot
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 ` syzbot [this message]
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=6836c371.a70a0220.253bc2.00c4.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 \
/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.