From: syzbot <syzbot+810ea5febd3b79bdd384@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?] WARNING in btrfs_run_delayed_refs (2)
Date: Mon, 18 Sep 2023 01:39:35 -0700 [thread overview]
Message-ID: <000000000000ffccbc06059e1493@google.com> (raw)
In-Reply-To: <0000000000003a29fe05feb87e4e@google.com>
syzbot has bisected this issue to:
commit f8f210dc84709804c9f952297f2bfafa6ea6b4bd
Author: Filipe Manana <fdmanana@suse.com>
Date: Tue Mar 21 11:13:59 2023 +0000
btrfs: calculate the right space for delayed refs when updating global reserve
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12fb487fa80000
start commit: dad9774deaf1 Merge tag 'timers-urgent-2023-06-21' of git:/..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11fb487fa80000
console output: https://syzkaller.appspot.com/x/log.txt?x=16fb487fa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e74b395fe4978721
dashboard link: https://syzkaller.appspot.com/bug?extid=810ea5febd3b79bdd384
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13ceaa3f280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1502f600a80000
Reported-by: syzbot+810ea5febd3b79bdd384@syzkaller.appspotmail.com
Fixes: f8f210dc8470 ("btrfs: calculate the right space for delayed refs when updating global reserve")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-09-18 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 14:13 [syzbot] [btrfs?] WARNING in btrfs_run_delayed_refs (2) syzbot
2023-09-18 8:39 ` 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=000000000000ffccbc06059e1493@google.com \
--to=syzbot+810ea5febd3b79bdd384@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 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.