From: syzbot <syzbot+dfcbc1741488709db4b2@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?] UBSAN: shift-out-of-bounds in __f2fs_commit_super
Date: Wed, 30 Sep 2026 06:53:02 -0700 [thread overview]
Message-ID: <6abd143e.fac9d4e5.17396.0003.GAE@google.com> (raw)
In-Reply-To: <784ebcc3-2d37-4640-88fa-3385a646c2d5@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+dfcbc1741488709db4b2@syzkaller.appspotmail.com
Tested-by: syzbot+dfcbc1741488709db4b2@syzkaller.appspotmail.com
Tested on:
commit: 7d114d27 f2fs: fix to set sbi->log_blocksize in advance
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
console output: https://syzkaller.appspot.com/x/log.txt?x=17652b15580000
kernel config: https://syzkaller.appspot.com/x/.config?x=40ee55a747aeff44
dashboard link: https://syzkaller.appspot.com/bug?extid=dfcbc1741488709db4b2
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-09-30 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 5:00 [f2fs-dev] [syzbot] [f2fs?] UBSAN: shift-out-of-bounds in __f2fs_commit_super syzbot
2026-09-30 8:55 ` Chao Yu via Linux-f2fs-devel
2026-09-30 13:53 ` 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=6abd143e.fac9d4e5.17396.0003.GAE@google.com \
--to=syzbot+dfcbc1741488709db4b2@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.