From: syzbot <syzbot+ebdb2403435c4136db2b@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?] WARNING in btrfs_run_delayed_refs
Date: Thu, 09 Mar 2023 03:57:17 -0800 [thread overview]
Message-ID: <000000000000a5202905f6765872@google.com> (raw)
In-Reply-To: <0000000000004c06c405eb318db4@google.com>
syzbot suspects this issue was fixed by commit:
commit 8bb808c6ad91ec3d332f072ce8f8aa4b16e307e0
Author: David Sterba <dsterba@suse.com>
Date: Thu Nov 3 13:39:01 2022 +0000
btrfs: don't print stack trace when transaction is aborted due to ENOMEM
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1541ad14c80000
start commit: 98555239e4c3 Merge tag 'arc-6.1-fixes' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=ebdb2403435c4136db2b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a4d8ea880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13172832880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: don't print stack trace when transaction is aborted due to ENOMEM
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-03-09 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 2:15 [syzbot] WARNING in btrfs_run_delayed_refs syzbot
2023-03-09 11:57 ` syzbot [this message]
2023-03-14 10:34 ` [syzbot] [btrfs?] " Dmitry Vyukov
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=000000000000a5202905f6765872@google.com \
--to=syzbot+ebdb2403435c4136db2b@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 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 NNTP newsgroup(s).