From: syzbot <syzbot+da0fc229cc1ff4bb2e6d@syzkaller.appspotmail.com>
To: agruenba@redhat.com, cluster-devel@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
rpeterso@redhat.com, swhiteho@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] BUG: unable to handle kernel NULL pointer dereference in gfs2_rgrp_dump
Date: Mon, 28 Aug 2023 17:46:32 -0700 [thread overview]
Message-ID: <0000000000006e8bd80604052481@google.com> (raw)
In-Reply-To: <000000000000b37bea05f0c125be@google.com>
syzbot has bisected this issue to:
commit 72244b6bc752b5c496f09de9a13c18adc314a53c
Author: Bob Peterson <rpeterso@redhat.com>
Date: Wed Aug 15 17:09:49 2018 +0000
gfs2: improve debug information when lvb mismatches are found
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1593747ba80000
start commit: 0a924817d2ed Merge tag '6.2-rc-smb3-client-fixes-part2' of..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1793747ba80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1393747ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76
dashboard link: https://syzkaller.appspot.com/bug?extid=da0fc229cc1ff4bb2e6d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e5bf7f880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13952f5d880000
Reported-by: syzbot+da0fc229cc1ff4bb2e6d@syzkaller.appspotmail.com
Fixes: 72244b6bc752 ("gfs2: improve debug information when lvb mismatches are found")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+da0fc229cc1ff4bb2e6d@syzkaller.appspotmail.com>
To: agruenba@redhat.com, cluster-devel@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
rpeterso@redhat.com, swhiteho@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [Cluster-devel] [syzbot] [gfs2?] BUG: unable to handle kernel NULL pointer dereference in gfs2_rgrp_dump
Date: Mon, 28 Aug 2023 17:46:32 -0700 [thread overview]
Message-ID: <0000000000006e8bd80604052481@google.com> (raw)
In-Reply-To: <000000000000b37bea05f0c125be@google.com>
syzbot has bisected this issue to:
commit 72244b6bc752b5c496f09de9a13c18adc314a53c
Author: Bob Peterson <rpeterso@redhat.com>
Date: Wed Aug 15 17:09:49 2018 +0000
gfs2: improve debug information when lvb mismatches are found
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1593747ba80000
start commit: 0a924817d2ed Merge tag '6.2-rc-smb3-client-fixes-part2' of..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1793747ba80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1393747ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76
dashboard link: https://syzkaller.appspot.com/bug?extid=da0fc229cc1ff4bb2e6d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e5bf7f880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13952f5d880000
Reported-by: syzbot+da0fc229cc1ff4bb2e6d@syzkaller.appspotmail.com
Fixes: 72244b6bc752 ("gfs2: improve debug information when lvb mismatches are found")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-29 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 20:40 [syzbot] [gfs2?] BUG: unable to handle kernel NULL pointer dereference in gfs2_rgrp_dump syzbot
2022-12-26 20:40 ` [Cluster-devel] " syzbot
2023-08-29 0:46 ` syzbot [this message]
2023-08-29 0:46 ` syzbot
2023-11-05 14:34 ` [syzbot] Null ptr deref syzbot
[not found] <CAK6rUAP-bopjVvGxevFKHEgVhYPxQMD-b2TGsmf81QWSYsirvQ@mail.gmail.com>
2023-11-05 15:41 ` [syzbot] [gfs2?] BUG: unable to handle kernel NULL pointer dereference in gfs2_rgrp_dump 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=0000000000006e8bd80604052481@google.com \
--to=syzbot+da0fc229cc1ff4bb2e6d@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=swhiteho@redhat.com \
--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.