From: syzbot <syzbot+eaa05fbc7563874b7ad2@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, fdmanana@suse.com,
josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] INFO: task hung in lock_extent
Date: Sun, 14 Apr 2024 01:41:02 -0700 [thread overview]
Message-ID: <0000000000000bef2806160a776f@google.com> (raw)
In-Reply-To: <0000000000000946cf05f34e12c2@google.com>
syzbot suspects this issue was fixed by commit:
commit b0ad381fa7690244802aed119b478b4bdafc31dd
Author: Josef Bacik <josef@toxicpanda.com>
Date: Mon Feb 12 16:56:02 2024 +0000
btrfs: fix deadlock with fiemap and extent locking
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=101316f5180000
start commit: 7521f258ea30 Merge tag 'mm-hotfixes-stable-2024-02-10-11-1..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=89a5d896b14c4565
dashboard link: https://syzkaller.appspot.com/bug?extid=eaa05fbc7563874b7ad2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c0d1e0180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10aff5b8180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: fix deadlock with fiemap and extent locking
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-04-14 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 7:38 [syzbot] [btrfs?] INFO: task hung in lock_extent syzbot
2024-04-14 8:41 ` syzbot [this message]
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=0000000000000bef2806160a776f@google.com \
--to=syzbot+eaa05fbc7563874b7ad2@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).