loop0: detected capacity change from 0 to 32768 bcachefs (baafa011-d992-4344-aaf9-4ff0e0bec0ff): Using encoding defined by superblock: utf8-12.1.0 bcachefs (loop0): starting version 1.7: mi_btree_bitmap opts=metadata_checksum=none,data_checksum=none,compression=lz4,nojournal_transaction_names allowing incompatible features above 0.0: (unknown version) bcachefs (loop0): invalid bkey in superblock btree=extents level=0: u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq 4e0410879b0c2f04 written 16 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0 invalid key type for btree extents (btree_ptr_v2), deleting bcachefs (loop0): recovering from clean shutdown, journal seq 13 bcachefs (loop0): Version upgrade required: Version upgrade from 0.19: freespace to 1.7: mi_btree_bitmap incomplete Doing incompatible version upgrade from 0.19: freespace to 1.25: extent_flags running recovery passes: check_allocations,check_alloc_info,check_lrus,check_btree_backpointers,check_backpointers_to_extents,check_extents_to_backpointers,check_alloc_to_lru_refs,bucket_gens_init,check_snapshot_trees,check_snapshots,check_subvols,check_subvol_children,delete_dead_snapshots,check_inodes,check_extents,check_indirect_extents,check_dirents,check_xattrs,check_root,check_unreachable_inodes,check_subvolume_structure,check_directory_structure,check_nlinks,set_fs_needs_rebalance bcachefs (loop0): bcachefs (loop0): error validating btree node on loop0 at btree inodes level 0/0 u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq 2a20405ac3f40602 written 24 min_key POS_MIN durability: 1 ptr: 0:38:0 gen 0 node offset 16/24 bset u64s 110: checksum error, type chacha20_poly1305_128: got ae8f36228b18163b56c0d80b3774aa58 should be d1e256903dc89dd6436b0db8b45d2093, shutting down error not marked as autofix and not in fsck run fsck, and forward to devs so error can be marked for self-healing inconsistency detected - emergency read only at journal seq 13 bcachefs (loop0): flagging btree inodes lost data bcachefs (loop0): running explicit recovery pass check_topology (2), currently at recovery_pass_empty (0) bcachefs (loop0): running explicit recovery pass scan_for_btree_nodes (1), currently at recovery_pass_empty (0) bcachefs (loop0): error reading btree root btree=inodes level=0: btree_node_read_error, fixing ================================================================== BUG: KASAN: use-after-free in poly1305_update include/crypto/poly1305.h:83 [inline] BUG: KASAN: use-after-free in bch2_checksum+0x209/0x490 fs/bcachefs/checksum.c:157 Read of size 8 at addr ffff888054d62870 by task syz.0.0/5317 CPU: 0 UID: 0 PID: 5317 Comm: syz.0.0 Not tainted 6.15.0-rc5-syzkaller-00043-gd76bb1ebb558 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xb4/0x290 mm/kasan/report.c:521 kasan_report+0x118/0x150 mm/kasan/report.c:634 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x29a/0x2b0 mm/kasan/generic.c:189 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 poly1305_update include/crypto/poly1305.h:83 [inline] bch2_checksum+0x209/0x490 fs/bcachefs/checksum.c:157 bch2_btree_node_read_done+0x1003/0x5470 fs/bcachefs/btree_io.c:1132 btree_node_read_work+0x565/0xef0 fs/bcachefs/btree_io.c:1366 bch2_btree_node_read+0x2151/0x27a0 fs/bcachefs/btree_io.c:-1 __bch2_btree_root_read fs/bcachefs/btree_io.c:1797 [inline] bch2_btree_root_read+0x5e7/0x750 fs/bcachefs/btree_io.c:1819 read_btree_roots+0x2cb/0x800 fs/bcachefs/recovery.c:582 bch2_fs_recovery+0x2356/0x37b0 fs/bcachefs/recovery.c:929 bch2_fs_start+0x70b/0xae0 fs/bcachefs/super.c:1091 bch2_fs_get_tree+0xd99/0x13a0 fs/bcachefs/fs.c:2570 vfs_get_tree+0x8f/0x2b0 fs/super.c:1759 do_new_mount+0x24a/0xa40 fs/namespace.c:3884 do_mount fs/namespace.c:4224 [inline] __do_sys_mount fs/namespace.c:4435 [inline] __se_sys_mount+0x317/0x410 fs/namespace.c:4412 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fc18859010a Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fc1893abe68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007fc1893abef0 RCX: 00007fc18859010a RDX: 0000200000000080 RSI: 0000200000000200 RDI: 00007fc1893abeb0 RBP: 0000200000000080 R08: 00007fc1893abef0 R09: 0000000002818414 R10: 0000000002818414 R11: 0000000000000246 R12: 0000200000000200 R13: 00007fc1893abeb0 R14: 000000000000f639 R15: 0000200000000140 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x54d62 flags: 0x4fff00000000000(node=1|zone=1|lastcpupid=0x7ff) raw: 04fff00000000000 ffffea0001535908 ffffea0001535808 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner info is not present (never set?) Memory state around the buggy address: ffff888054d62700: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888054d62780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888054d62800: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888054d62880: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888054d62900: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================