From: syzbot <syzbot+b12826218502df019f9d@syzkaller.appspotmail.com>
To: agruenba@redhat.com, gfs2@lists.linux.dev,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] KASAN: null-ptr-deref Read in gfs2_drop_inode
Date: Mon, 26 May 2025 20:19:03 -0700 [thread overview]
Message-ID: <68352f27.a70a0220.253bc2.009f.GAE@google.com> (raw)
In-Reply-To: <68344a84.a70a0220.1765ec.0166.GAE@google.com>
syzbot has bisected this issue to:
commit ae9f3bd8259a0a8f67be2420e66bb05fbb95af48
Author: Andreas Gruenbacher <agruenba@redhat.com>
Date: Sat Apr 5 22:31:37 2025 +0000
gfs2: replace sd_aspace with sd_inode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1042cdf4580000
start commit: 176e917e010c Add linux-next specific files for 20250523
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1242cdf4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1442cdf4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e7902c752bef748
dashboard link: https://syzkaller.appspot.com/bug?extid=b12826218502df019f9d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=151759f4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b9c5f4580000
Reported-by: syzbot+b12826218502df019f9d@syzkaller.appspotmail.com
Fixes: ae9f3bd8259a ("gfs2: replace sd_aspace with sd_inode")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-05-27 3:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 11:03 [syzbot] [gfs2?] KASAN: null-ptr-deref Read in gfs2_drop_inode syzbot
2025-05-27 3:19 ` syzbot [this message]
2025-06-02 12:05 ` [syzbot] " syzbot
[not found] <6cf69815-db19-45f3-99f0-9879ed5f02c2@redhat.com>
2025-06-02 13:33 ` 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=68352f27.a70a0220.253bc2.009f.GAE@google.com \
--to=syzbot+b12826218502df019f9d@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--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.