public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+69f5379a1717a0b982a1@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 read_inline_xattr
Date: Sun, 22 Dec 2024 23:52:03 -0800	[thread overview]
Message-ID: <676916a3.050a0220.2f3838.0017.GAE@google.com> (raw)
In-Reply-To: <674f4e7d.050a0220.17bd51.004f.GAE@google.com>

syzbot has bisected this issue to:

commit 388a2a0640e16a8887f0d47dab207f344fbdb913
Author: Chao Yu <chao@kernel.org>
Date:   Thu Jun 6 09:55:51 2024 +0000

    f2fs: remove redundant sanity check in sanity_check_inode()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14bffcf8580000
start commit:   bcde95ce32b6 Merge tag 'devicetree-fixes-for-6.13-1' of gi..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=16bffcf8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=12bffcf8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1234f097ee657d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=69f5379a1717a0b982a1
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=112b98c4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16fd7cf8580000

Reported-by: syzbot+69f5379a1717a0b982a1@syzkaller.appspotmail.com
Fixes: 388a2a0640e1 ("f2fs: remove redundant sanity check in sanity_check_inode()")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2024-12-23  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 18:31 [syzbot] [f2fs?] UBSAN: array-index-out-of-bounds in read_inline_xattr syzbot
2024-12-22 19:13 ` syzbot
2024-12-23 14:13   ` Chao Yu
2024-12-23 21:30     ` syzbot
2024-12-26 14:02   ` Chao Yu
2024-12-26 15:02     ` syzbot
2024-12-23  7:52 ` 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=676916a3.050a0220.2f3838.0017.GAE@google.com \
    --to=syzbot+69f5379a1717a0b982a1@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