mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+a77d690840e60bc2ddd8@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dmantipov@yandex.ru,
	heming.zhao@suse.com,  jlbec@evilplan.org,
	joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org,
	 mark@fasheh.com, ocfs2-devel@lists.linux.dev,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KASAN: slab-out-of-bounds Read in igrab
Date: Fri, 07 Nov 2025 15:24:03 -0800	[thread overview]
Message-ID: <690e7f93.a70a0220.22f260.006a.GAE@google.com> (raw)
In-Reply-To: <68ac2451.050a0220.37038e.008b.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit fe7a283b39160153b6d1bd7f61b0a9d5d44987a8
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Tue Aug 26 09:51:06 2025 +0000

    ocfs2: add suballoc slot check in ocfs2_validate_inode_block()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14c14412580000
start commit:   6debb6904172 Merge tag 'drm-fixes-2025-08-23-1' of https:/..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=e1e1566c7726877e
dashboard link: https://syzkaller.appspot.com/bug?extid=a77d690840e60bc2ddd8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1248cc42580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: ocfs2: add suballoc slot check in ocfs2_validate_inode_block()

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

  parent reply	other threads:[~2025-11-07 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25  8:52 syzbot
2025-08-26  7:23 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git 5b1ae9de71335865d06ff0e60eadcf368a735edf syzbot
2025-11-07 23:24 ` syzbot [this message]
     [not found] <95cdfe52-cb32-44e8-87ce-1f23710b5f21@yandex.ru>
2025-08-26 10:47 ` [syzbot] [ocfs2?] KASAN: slab-out-of-bounds Read in igrab 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=690e7f93.a70a0220.22f260.006a.GAE@google.com \
    --to=syzbot+a77d690840e60bc2ddd8@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmantipov@yandex.ru \
    --cc=heming.zhao@suse.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --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
all inboxes | Powered by JetHome®