All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d6443e1f040e8d616e7b@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?] kernel BUG in btrfs_cancel_balance
Date: Tue, 01 Aug 2023 04:56:56 -0700	[thread overview]
Message-ID: <000000000000672c810601db3e84@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    57012c57536f Merge tag 'net-6.5-rc4' of git://git.kernel.o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1413a086a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5d10d93e1ae1f229
dashboard link: https://syzkaller.appspot.com/bug?extid=d6443e1f040e8d616e7b
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=137d82cea80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7336195c1d93/disk-57012c57.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e7a6562e4033/vmlinux-57012c57.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7d66531ff83b/bzImage-57012c57.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e6f09fca3191/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d6443e1f040e8d616e7b@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/btrfs/volumes.c:4642!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5160 Comm: syz-executor.1 Not tainted 6.5.0-rc3-syzkaller-00123-g57012c57536f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
RIP: 0010:btrfs_cancel_balance+0x429/0x430 fs/btrfs/volumes.c:4641
Code: e8 1c 31 01 00 4c 89 ef 48 c7 c6 00 fd 4a 8b e8 ad 1a 24 07 e9 ef fe ff ff e8 a3 af 25 07 e8 3e 04 f5 fd 0f 0b e8 37 04 f5 fd <0f> 0b 0f 1f 44 00 00 f3 0f 1e fa 55 48 89 e5 41 57 41 56 41 55 41
RSP: 0018:ffffc90004b7fdc0 EFLAGS: 00010293
RAX: ffffffff839711d9 RBX: ffff888063844010 RCX: ffff888079498000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffffc90004b7fed0 R08: ffff8880638453d3 R09: 1ffff1100c708a7a
R10: dffffc0000000000 R11: ffffed100c708a7b R12: 1ffff9200096ffc0
R13: ffff888063845468 R14: dffffc0000000000 R15: ffff888063845460
FS:  00007fab7440b6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1c1abfe000 CR3: 000000007aa05000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 btrfs_ioctl_balance_ctl+0x3f/0x70 fs/btrfs/ioctl.c:3632
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fab7367cb29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fab7440b0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fab7379c120 RCX: 00007fab7367cb29
RDX: 0000000000000002 RSI: 0000000040049421 RDI: 0000000000000006
RBP: 00007fab736c847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fab7379c120 R15: 00007ffcf21c7038
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:btrfs_cancel_balance+0x429/0x430 fs/btrfs/volumes.c:4641
Code: e8 1c 31 01 00 4c 89 ef 48 c7 c6 00 fd 4a 8b e8 ad 1a 24 07 e9 ef fe ff ff e8 a3 af 25 07 e8 3e 04 f5 fd 0f 0b e8 37 04 f5 fd <0f> 0b 0f 1f 44 00 00 f3 0f 1e fa 55 48 89 e5 41 57 41 56 41 55 41
RSP: 0018:ffffc90004b7fdc0 EFLAGS: 00010293

RAX: ffffffff839711d9 RBX: ffff888063844010 RCX: ffff888079498000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffffc90004b7fed0 R08: ffff8880638453d3 R09: 1ffff1100c708a7a
R10: dffffc0000000000 R11: ffffed100c708a7b R12: 1ffff9200096ffc0
R13: ffff888063845468 R14: dffffc0000000000 R15: ffff888063845460
FS:  00007fab7440b6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1c22cd71e5 CR3: 000000007aa05000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

             reply	other threads:[~2023-08-01 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 11:56 syzbot [this message]
2023-08-02  3:17 ` [syzbot] [btrfs?] kernel BUG in btrfs_cancel_balance syzbot
2023-08-02 14:35 ` syzbot
2023-08-20 16:31 ` Siddh Raman Pant
2023-08-20 16:31   ` syzbot
2023-08-20 17:16   ` syzbot
2023-10-01  0:03 ` syzbot

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=000000000000672c810601db3e84@google.com \
    --to=syzbot+d6443e1f040e8d616e7b@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 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.