From: syzbot <syzbot+52d708a0bca2efc4c9df@syzkaller.appspotmail.com>
To: anand.jain@oracle.com, clm@fb.com, dsterba@suse.com,
hdanton@sina.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in btrfs_commit_transaction
Date: Sun, 29 Jan 2023 00:00:22 -0800 [thread overview]
Message-ID: <00000000000091f75805f3627ddd@google.com> (raw)
In-Reply-To: <00000000000076699c05ed7c54a2@google.com>
syzbot suspects this issue was fixed by commit:
commit b740d806166979488e798e41743aaec051f2443f
Author: Josef Bacik <josef@toxicpanda.com>
Date: Mon Nov 7 16:44:51 2022 +0000
btrfs: free btrfs_path before copying root refs to userspace
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14e58bae480000
start commit: 08ad43d554ba Merge tag 'net-6.1-rc7' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8d01b6e3197974dd
dashboard link: https://syzkaller.appspot.com/bug?extid=52d708a0bca2efc4c9df
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114d3e03880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1320ea4b880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: free btrfs_path before copying root refs to userspace
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-29 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 6:18 [syzbot] possible deadlock in btrfs_commit_transaction syzbot
2023-01-29 8:00 ` syzbot [this message]
2023-01-30 8:47 ` Dmitry Vyukov
[not found] <20221115123800.2680-1-hdanton@sina.com>
2022-11-15 23:14 ` 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=00000000000091f75805f3627ddd@google.com \
--to=syzbot+52d708a0bca2efc4c9df@syzkaller.appspotmail.com \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hdanton@sina.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@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 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.