From: syzbot <syzbot+4406ed3884d139266b67@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in btrfs_sync_log
Date: Sun, 16 Oct 2022 13:36:42 -0700 [thread overview]
Message-ID: <000000000000186e6c05eb2cd12e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 493ffd6605b2 Merge tag 'ucount-rlimits-cleanups-for-v5.19'..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c65b84880000
kernel config: https://syzkaller.appspot.com/x/.config?x=d19f5d16783f901
dashboard link: https://syzkaller.appspot.com/bug?extid=4406ed3884d139266b67
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, 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/f1ff6481e26f/disk-493ffd66.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/101bd3c7ae47/vmlinux-493ffd66.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4406ed3884d139266b67@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 32768
BTRFS info (device loop0): using xxhash64 (xxhash64-generic) checksum algorithm
BTRFS info (device loop0): using free space tree
BTRFS info (device loop0): enabling ssd optimizations
------------[ cut here ]------------
WARNING: CPU: 0 PID: 30197 at fs/btrfs/tree-log.c:3081 btrfs_sync_log+0x1ebd/0x2d40 fs/btrfs/tree-log.c:3081
Modules linked in:
CPU: 0 PID: 30197 Comm: syz-executor.0 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:btrfs_sync_log+0x1ebd/0x2d40 fs/btrfs/tree-log.c:3081
Code: 2b 42 92 06 49 be 00 00 00 00 00 fc ff df 4c 8b 64 24 40 eb 19 e8 d3 a0 f4 fd 48 c7 c7 60 f5 db 8a 89 de 31 c0 e8 33 05 bd fd <0f> 0b b3 01 44 0f b6 c3 4c 89 e7 48 c7 c6 e0 f5 db 8a ba 09 0c 00
RSP: 0018:ffffc90004ed74a0 EFLAGS: 00010246
RAX: db16f372e186ad00 RBX: 00000000fffffff4 RCX: 0000000000040000
RDX: ffffc90004022000 RSI: 000000000000385b RDI: 000000000000385c
RBP: ffffc90004ed7930 R08: ffffffff816aa79d R09: ffffed1017344f13
R10: ffffed1017344f13 R11: 1ffff11017344f12 R12: ffff88808a1dd540
R13: 00000000fffffff4 R14: dffffc0000000000 R15: ffff88808a1dd590
FS: 00007f7877fdd700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3761c46000 CR3: 0000000079795000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_sync_file+0xdf4/0x1140 fs/btrfs/file.c:2242
generic_write_sync include/linux/fs.h:2873 [inline]
btrfs_do_write_iter+0xa6f/0x1370 fs/btrfs/file.c:1975
call_write_iter include/linux/fs.h:2190 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x7dc/0xc50 fs/read_write.c:584
ksys_write+0x177/0x2a0 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7876e8b5a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7877fdd168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f7876fabf80 RCX: 00007f7876e8b5a9
RDX: 0000000000000010 RSI: 0000000020000080 RDI: 0000000000000004
RBP: 00007f7877fdd1d0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007ffca3e1f08f R14: 00007f7877fdd300 R15: 0000000000022000
</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.
next reply other threads:[~2022-10-16 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 20:36 syzbot [this message]
2022-11-01 17:41 ` [syzbot] WARNING in btrfs_sync_log syzbot
2024-05-16 20:31 ` David Sterba
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=000000000000186e6c05eb2cd12e@google.com \
--to=syzbot+4406ed3884d139266b67@syzkaller.appspotmail.com \
--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=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.