From: syzbot <syzbot+bfbc1eecdfb9b10e5792@syzkaller.appspotmail.com>
To: dchinner@redhat.com, djwong@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] general protection fault in __xfs_free_extent
Date: Sun, 28 May 2023 05:10:30 -0700 [thread overview]
Message-ID: <0000000000003ccc9b05fcbfdb68@google.com> (raw)
In-Reply-To: <000000000000540fc405f01401bf@google.com>
syzbot suspects this issue was fixed by commit:
commit b2ccab3199aa7cea9154d80ea2585312c5f6eba0
Author: Darrick J. Wong <djwong@kernel.org>
Date: Wed Apr 12 01:59:53 2023 +0000
xfs: pass per-ag references to xfs_free_extent
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1007e5c1280000
start commit: 02bf43c7b7f7 Merge tag 'fs.xattr.simple.rework.rbtree.rwlo..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8c59170b68d26a55
dashboard link: https://syzkaller.appspot.com/bug?extid=bfbc1eecdfb9b10e5792
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1798429d880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161b948f880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xfs: pass per-ag references to xfs_free_extent
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2023-05-28 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000540fc405f01401bf@google.com>
2023-05-28 12:10 ` syzbot [this message]
2023-05-30 9:58 ` [syzbot] [xfs?] general protection fault in __xfs_free_extent Aleksandr Nogikh
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=0000000000003ccc9b05fcbfdb68@google.com \
--to=syzbot+bfbc1eecdfb9b10e5792@syzkaller.appspotmail.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).