From: syzbot <syzbot+b4cb4a6988aced0cec4b@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [bcachefs?] kernel BUG in bch2_reconstruct_snapshots
Date: Sun, 16 Feb 2025 23:53:27 -0800 [thread overview]
Message-ID: <67b2eaf7.050a0220.173698.001f.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 128c8f96eb86 Merge tag 'drm-fixes-2025-02-14' of https://g..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13c44bf8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e55cabe422b4fcaf
dashboard link: https://syzkaller.appspot.com/bug?extid=b4cb4a6988aced0cec4b
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=16d5d9b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=112099a4580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/419cba1a156b/disk-128c8f96.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0fa327c9a058/vmlinux-128c8f96.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5ad066f8a08b/bzImage-128c8f96.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/77719351875e/mount_0.gz
The issue was bisected to:
commit c986dd7ecba185ad2a36b0815940f34deb2a8170
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Thu Oct 10 01:28:11 2024 +0000
bcachefs: Improve check_snapshot_exists()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1568e098580000
final oops: https://syzkaller.appspot.com/x/report.txt?x=1768e098580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1368e098580000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b4cb4a6988aced0cec4b@syzkaller.appspotmail.com
Fixes: c986dd7ecba1 ("bcachefs: Improve check_snapshot_exists()")
bcachefs (loop0): scanning for missing backpointers in 6/128 buckets
done
bcachefs (loop0): reconstruct_snapshots...
snapshot node 4294905343 from tree 4294905343 missing, recreating
------------[ cut here ]------------
kernel BUG at fs/bcachefs/bkey_types.h:210!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 5822 Comm: syz-executor354 Not tainted 6.14.0-rc2-syzkaller-00185-g128c8f96eb86 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:bkey_s_c_to_subvolume fs/bcachefs/bkey_types.h:210 [inline]
RIP: 0010:check_snapshot_exists fs/bcachefs/snapshot.c:884 [inline]
RIP: 0010:bch2_reconstruct_snapshots+0x35a5/0x35b0 fs/bcachefs/snapshot.c:1001
Code: 08 a9 fd e9 e3 cb ff ff e8 88 51 44 fd e8 f3 fa a8 fd 4c 89 ef 89 de e8 29 68 cc ff e8 74 51 44 fd 90 0f 0b e8 6c 51 44 fd 90 <0f> 0b e8 84 e7 82 07 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90003dfee20 EFLAGS: 00010293
RAX: ffffffff847d6594 RBX: 0000000000000009 RCX: ffff88807c9d5a00
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 0000000000000015
RBP: ffffc90003dff428 R08: ffffffff847d56ba R09: 0000000000000000
R10: ffffc90003dfe820 R11: fffff520007bfd11 R12: ffff8880250865c0
R13: 0000000000000000 R14: ffff888029330230 R15: 1ffff11004a10cb8
FS: 000055558bf6c380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055da28eea000 CR3: 000000005d824000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
bch2_run_recovery_pass+0xf0/0x1e0 fs/bcachefs/recovery_passes.c:226
bch2_run_recovery_passes+0x2ad/0xa90 fs/bcachefs/recovery_passes.c:291
bch2_fs_recovery+0x265a/0x3de0 fs/bcachefs/recovery.c:936
bch2_fs_start+0x37c/0x610 fs/bcachefs/super.c:1041
bch2_fs_get_tree+0xdb7/0x17a0 fs/bcachefs/fs.c:2203
vfs_get_tree+0x90/0x2b0 fs/super.c:1814
do_new_mount+0x2be/0xb40 fs/namespace.c:3560
do_mount fs/namespace.c:3900 [inline]
__do_sys_mount fs/namespace.c:4111 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4088
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe1e5e912ea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 5e 04 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007fff4e8847f8 EFLAGS: 00000282 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fff4e884810 RCX: 00007fe1e5e912ea
RDX: 00004000000058c0 RSI: 0000400000005900 RDI: 00007fff4e884810
RBP: 0000400000005900 R08: 00007fff4e884850 R09: 000000000000592e
R10: 0000000001000000 R11: 0000000000000282 R12: 00004000000058c0
R13: 00007fff4e884850 R14: 0000000000000003 R15: 0000000001000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:bkey_s_c_to_subvolume fs/bcachefs/bkey_types.h:210 [inline]
RIP: 0010:check_snapshot_exists fs/bcachefs/snapshot.c:884 [inline]
RIP: 0010:bch2_reconstruct_snapshots+0x35a5/0x35b0 fs/bcachefs/snapshot.c:1001
Code: 08 a9 fd e9 e3 cb ff ff e8 88 51 44 fd e8 f3 fa a8 fd 4c 89 ef 89 de e8 29 68 cc ff e8 74 51 44 fd 90 0f 0b e8 6c 51 44 fd 90 <0f> 0b e8 84 e7 82 07 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90003dfee20 EFLAGS: 00010293
RAX: ffffffff847d6594 RBX: 0000000000000009 RCX: ffff88807c9d5a00
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 0000000000000015
RBP: ffffc90003dff428 R08: ffffffff847d56ba R09: 0000000000000000
R10: ffffc90003dfe820 R11: fffff520007bfd11 R12: ffff8880250865c0
R13: 0000000000000000 R14: ffff888029330230 R15: 1ffff11004a10cb8
FS: 000055558bf6c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ff36f26038 CR3: 000000005d824000 CR4: 00000000003526f0
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.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
If the report is already addressed, 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 overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
next reply other threads:[~2025-02-17 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 7:53 syzbot [this message]
2025-06-19 18:11 ` [syzbot] [bcachefs?] kernel BUG in bch2_reconstruct_snapshots 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=67b2eaf7.050a0220.173698.001f.GAE@google.com \
--to=syzbot+b4cb4a6988aced0cec4b@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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.