From: syzbot <syzbot+d6443e1f040e8d616e7b@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@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?] kernel BUG in btrfs_cancel_balance
Date: Wed, 02 Aug 2023 07:35:31 -0700 [thread overview]
Message-ID: <00000000000060bb2a0601f1936f@google.com> (raw)
In-Reply-To: <000000000000672c810601db3e84@google.com>
syzbot has bisected this issue to:
commit b19c98f237cd76981aaded52c258ce93f7daa8cb
Author: Josef Bacik <josef@toxicpanda.com>
Date: Fri Jun 23 05:05:41 2023 +0000
btrfs: fix race between balance and cancel/pause
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12223eb9a80000
start commit: 5d0c230f1de8 Linux 6.5-rc4
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11223eb9a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=16223eb9a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1e3d5175079af5a4
dashboard link: https://syzkaller.appspot.com/bug?extid=d6443e1f040e8d616e7b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1167e711a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16a90161a80000
Reported-by: syzbot+d6443e1f040e8d616e7b@syzkaller.appspotmail.com
Fixes: b19c98f237cd ("btrfs: fix race between balance and cancel/pause")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-02 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 11:56 [syzbot] [btrfs?] kernel BUG in btrfs_cancel_balance syzbot
2023-08-02 3:17 ` syzbot
2023-08-02 14:35 ` syzbot [this message]
2023-08-20 16:31 ` Siddh Raman Pant
2023-08-20 16:31 ` syzbot
2023-08-20 17:16 ` syzbot
2023-10-01 0:03 ` 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=00000000000060bb2a0601f1936f@google.com \
--to=syzbot+d6443e1f040e8d616e7b@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@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 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.