From: syzbot <syzbot+3b6e67ac2b646da57862@syzkaller.appspotmail.com>
To: agruenba@redhat.com, eadavis@qq.com, gfs2@lists.linux.dev,
juntong.deng@outlook.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, rpeterso@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] kernel BUG in gfs2_quota_cleanup
Date: Sat, 02 Dec 2023 13:33:04 -0800 [thread overview]
Message-ID: <0000000000004ae32c060b8da1dc@google.com> (raw)
In-Reply-To: <000000000000f0bfe70605025941@google.com>
syzbot has bisected this issue to:
commit bdcb8aa434c6d36b5c215d02a9ef07551be25a37
Author: Juntong Deng <juntong.deng@outlook.com>
Date: Sun Oct 29 21:10:06 2023 +0000
gfs2: Fix slab-use-after-free in gfs2_qd_dealloc
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=169c7b52e80000
start commit: 994d5c58e50e Merge tag 'hardening-v6.7-rc4' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=159c7b52e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=119c7b52e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c2c74446ab4f0028
dashboard link: https://syzkaller.appspot.com/bug?extid=3b6e67ac2b646da57862
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1268c086e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=164b3faae80000
Reported-by: syzbot+3b6e67ac2b646da57862@syzkaller.appspotmail.com
Fixes: bdcb8aa434c6 ("gfs2: Fix slab-use-after-free in gfs2_qd_dealloc")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-12-02 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 14:51 [syzbot] [gfs2?] kernel BUG in gfs2_quota_cleanup syzbot
2023-12-01 23:57 ` syzbot
2023-12-02 9:25 ` [PATCH] gfs2: fix " Edward Adam Davis
2023-12-05 13:51 ` Andreas Gruenbacher
2023-12-02 4:18 ` [syzbot] [gfs2?] " syzbot
2023-12-02 21:33 ` syzbot [this message]
[not found] <tencent_FDD15365E367E96523A72445B769D77D8605@qq.com>
2023-12-02 6:26 ` 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=0000000000004ae32c060b8da1dc@google.com \
--to=syzbot+3b6e67ac2b646da57862@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=eadavis@qq.com \
--cc=gfs2@lists.linux.dev \
--cc=juntong.deng@outlook.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@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.