From: syzbot <syzbot+049b5ea03bae9d6acc9b@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: [syzbot] [btrfs?] WARNING in btrfs_mark_ordered_io_finished
Date: Thu, 20 Apr 2023 02:36:41 -0700 [thread overview]
Message-ID: <00000000000030932c05f9c1472f@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a7a55e27ad72 Merge tag 'i2c-for-6.3-rc7' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=104304fbc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=759d5e665e47a55
dashboard link: https://syzkaller.appspot.com/bug?extid=049b5ea03bae9d6acc9b
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/89778cf51c73/disk-a7a55e27.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8d826c46f139/vmlinux-a7a55e27.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fb0e22b4bb2a/bzImage-a7a55e27.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+049b5ea03bae9d6acc9b@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1070 at fs/btrfs/ordered-data.c:388 btrfs_mark_ordered_io_finished+0x993/0xcf0
Modules linked in:
CPU: 1 PID: 1070 Comm: kworker/u4:5 Not tainted 6.3.0-rc6-syzkaller-00183-ga7a55e27ad72 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Workqueue: events_unbound btrfs_async_reclaim_metadata_space
RIP: 0010:btrfs_mark_ordered_io_finished+0x993/0xcf0 fs/btrfs/ordered-data.c:388
Code: f8 ff ff e8 af 8a fe fd 48 c7 c7 80 45 2a 8b 48 c7 c6 e0 43 2a 8b ba 71 01 00 00 e8 c7 fe 10 07 e9 06 fd ff ff e8 8d 8a fe fd <0f> 0b 48 8b 84 24 a0 00 00 00 42 80 3c 28 00 4c 8b 7c 24 68 74 0a
RSP: 0018:ffffc90005cfee98 EFLAGS: 00010093
RAX: ffffffff838bec33 RBX: 00000000000ca000 RCX: ffff8880212a1d40
RDX: 0000000000000000 RSI: 00000000000ca000 RDI: 0000000000085000
RBP: fffffffffffbb000 R08: ffffffff838be9b7 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: 1ffff110048753ad
R13: dffffc0000000000 R14: 0000000000002000 R15: 00000000000ca000
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32025000 CR3: 000000002ec18000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_run_delalloc_range+0xee2/0x11d0 fs/btrfs/inode.c:2258
writepage_delalloc+0x261/0x590 fs/btrfs/extent_io.c:1424
__extent_writepage+0x850/0x16d0 fs/btrfs/extent_io.c:1724
extent_write_cache_pages fs/btrfs/extent_io.c:2635 [inline]
extent_writepages+0xc31/0x1930 fs/btrfs/extent_io.c:2755
do_writepages+0x3a6/0x670 mm/page-writeback.c:2551
filemap_fdatawrite_wbc+0x125/0x180 mm/filemap.c:390
start_delalloc_inodes+0x7e1/0xcb0 fs/btrfs/inode.c:9287
btrfs_start_delalloc_roots+0x745/0xab0 fs/btrfs/inode.c:9366
shrink_delalloc fs/btrfs/space-info.c:611 [inline]
flush_space+0x61d/0xe30 fs/btrfs/space-info.c:719
btrfs_async_reclaim_metadata_space+0x29f/0x350 fs/btrfs/space-info.c:1066
process_one_work+0x8a0/0x10e0 kernel/workqueue.c:2390
worker_thread+0xa63/0x1210 kernel/workqueue.c:2537
kthread+0x270/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2023-04-20 9:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00000000000030932c05f9c1472f@google.com \
--to=syzbot+049b5ea03bae9d6acc9b@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
all inboxes | Powered by JetHome®