From: syzbot <syzbot+e4876215632c2d23b481@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?] UBSAN: array-index-out-of-bounds in inline_xattr_addr
Date: Sun, 22 Dec 2024 12:55:02 -0800 [thread overview]
Message-ID: <67687ca6.050a0220.2f3838.000b.GAE@google.com> (raw)
In-Reply-To: <3768d492-8de1-4165-948c-192054ff051b@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+e4876215632c2d23b481@syzkaller.appspotmail.com
Tested-by: syzbot+e4876215632c2d23b481@syzkaller.appspotmail.com
Tested on:
commit: a108daa4 f2fs: fix to avoid out-of-bounds access in f2..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
console output: https://syzkaller.appspot.com/x/log.txt?x=17ef98c4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd60186d08e947a5
dashboard link: https://syzkaller.appspot.com/bug?extid=e4876215632c2d23b481
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-12-22 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 1:56 [syzbot] [f2fs?] UBSAN: array-index-out-of-bounds in inline_xattr_addr syzbot
2024-12-20 11:28 ` [syzbot] Re: UBSAN: array-index-out-of-bounds in inline_xattr_addr() syzbot
2024-12-22 13:38 ` [syzbot] [f2fs?] UBSAN: array-index-out-of-bounds in inline_xattr_addr Chao Yu
2024-12-22 13:38 ` syzbot
2024-12-22 13:57 ` Chao Yu
2024-12-22 20:55 ` syzbot [this message]
2025-02-11 6:46 ` Chao Yu
[not found] <20241220112852.sWPOO%dmantipov@yandex.ru>
2024-12-20 16:50 ` 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=67687ca6.050a0220.2f3838.000b.GAE@google.com \
--to=syzbot+e4876215632c2d23b481@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox