From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+c06034aecf9f5eab1ac1@syzkaller.appspotmail.com>
Cc: anand.jain@oracle.com, clm@fb.com, dsterba@suse.com,
hdanton@sina.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?] possible deadlock in btrfs_search_slot
Date: Wed, 2 Aug 2023 16:17:22 +0200 [thread overview]
Message-ID: <CANp29Y5DKbC0oCcxoX-fST0LQ8=0KZ-RK-GXL=2Vw=3y++wtOw@mail.gmail.com> (raw)
In-Reply-To: <000000000000261e660601dec2c2@google.com>
On Tue, Aug 1, 2023 at 6:08 PM syzbot
<syzbot+c06034aecf9f5eab1ac1@syzkaller.appspotmail.com> wrote:
>
> 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=13015709a80000
> start commit: eb7081409f94 Linux 6.1-rc6
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=8d01b6e3197974dd
> dashboard link: https://syzkaller.appspot.com/bug?extid=c06034aecf9f5eab1ac1
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=124fc309880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=126dfde5880000
>
> 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
Looks reasonable.
#syz fix: btrfs: free btrfs_path before copying root refs to userspace
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
prev parent reply other threads:[~2023-08-02 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 18:29 [syzbot] possible deadlock in btrfs_search_slot syzbot
2022-11-23 21:12 ` syzbot
2023-08-01 16:08 ` [syzbot] [btrfs?] " syzbot
2023-08-02 14:17 ` Aleksandr Nogikh [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='CANp29Y5DKbC0oCcxoX-fST0LQ8=0KZ-RK-GXL=2Vw=3y++wtOw@mail.gmail.com' \
--to=nogikh@google.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-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+c06034aecf9f5eab1ac1@syzkaller.appspotmail.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.