From: David Sterba <dsterba@suse.cz>
To: syzbot <syzbot+9c37714c07194d816417@syzkaller.appspotmail.com>
Cc: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in btrfs_commit_transaction
Date: Wed, 2 Nov 2022 23:53:52 +0100 [thread overview]
Message-ID: <20221102225352.GJ5824@twin.jikos.cz> (raw)
In-Reply-To: <0000000000000c379205ec806d6e@google.com>
On Wed, Nov 02, 2022 at 10:46:53AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: b229b6ca5abb Merge tag 'perf-tools-fixes-for-v6.1-2022-10-..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=12db9c7e880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
> dashboard link: https://syzkaller.appspot.com/bug?extid=9c37714c07194d816417
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17401632880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13176716880000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/ba5b49fa77de/disk-b229b6ca.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/7c061f2ae4dc/vmlinux-b229b6ca.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/bc45c1300e9b/bzImage-b229b6ca.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/62077524a72d/mount_0.gz
>
> Bisection is inconclusive: the issue happens on the oldest tested release.
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14e432a6880000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=16e432a6880000
> console output: https://syzkaller.appspot.com/x/log.txt?x=12e432a6880000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+9c37714c07194d816417@syzkaller.appspotmail.com
>
> BTRFS info (device loop0): clearing compat-ro feature flag for FREE_SPACE_TREE (0x1)
> BTRFS info (device loop0): clearing compat-ro feature flag for FREE_SPACE_TREE_VALID (0x2)
> BTRFS info (device loop0): checking UUID tree
> BTRFS warning (device loop0): Skipping commit of aborted transaction.
> ------------[ cut here ]------------
> BTRFS: Transaction aborted (error -12)
-12 is ENOMEM, so another point for adding it to the list of exceptions
and not reporting the stacktrace. We have other warnings or assertions
to catch bad cleanup after errors.
next prev parent reply other threads:[~2022-11-02 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 17:46 syzbot
2022-11-02 22:53 ` David Sterba [this message]
2022-11-28 21:11 ` syzbot
2022-11-29 22:13 ` Marco Elver
2022-11-30 8:03 ` 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=20221102225352.GJ5824@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9c37714c07194d816417@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®