[<prev] [next>] [day] [month] [year] [list]
Message-ID: <67403130.050a0220.3c9d61.018b.GAE@google.com>
Date: Thu, 21 Nov 2024 23:22:24 -0800
From: syzbot <syzbot+61a8a372d9269e5c9c6d@...kaller.appspotmail.com>
To: kent.overstreet@...ux.dev, linux-bcachefs@...r.kernel.org,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [bcachefs?] WARNING in bch2_fs_read_write_early (2)
Hello,
syzbot found the following issue on:
HEAD commit: f66d6acccbc0 Merge tag 'x86_urgent_for_v6.12' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=171d3378580000
kernel config: https://syzkaller.appspot.com/x/.config?x=95b7d4b29182ed62
dashboard link: https://syzkaller.appspot.com/bug?extid=61a8a372d9269e5c9c6d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-f66d6acc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d4b910af2286/vmlinux-f66d6acc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a72e7698c7be/bzImage-f66d6acc.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+61a8a372d9269e5c9c6d@...kaller.appspotmail.com
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 3812 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 3570 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 3328 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 3086 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 2844 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 2602 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 2360 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 2118 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 1876 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 1634 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 1392 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 1150 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 908 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 666 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 424 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): error validating btree node at btree extents level 0/0
u64s 11 type btree_ptr_v2 SPOS_MAX len 0 ver 0: seq c6c25c03258c59c5 written 1032 min_key POS_MIN durability: 1 ptr: 0:27:0 gen 0
node offset 0/1032 bset u64s 182 bset byte offset 160: bad k->u64s 0 (min 3 max 253), fixing
bcachefs (loop0): btree_node_read_work: rewriting btree node at btree=extents level=0 SPOS_MAX due to error
------------[ cut here ]------------
WARNING: CPU: 0 PID: 37 at fs/bcachefs/super.c:526 bch2_fs_read_write_early+0x7f/0xb0 fs/bcachefs/super.c:526
Modules linked in:
CPU: 0 UID: 0 PID: 37 Comm: kworker/0:1H Not tainted 6.12.0-rc7-syzkaller-00216-gf66d6acccbc0 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: bcachefs_btree_read_complete btree_node_read_work
RIP: 0010:bch2_fs_read_write_early+0x7f/0xb0 fs/bcachefs/super.c:526
Code: e8 46 74 48 fd 85 ed 74 1b e8 fd 6f 48 fd eb 05 e8 f6 6f 48 fd 48 89 df be 01 00 00 00 5b 5d e9 07 fc ff ff e8 e2 6f 48 fd 90 <0f> 0b 90 eb e6 48 c7 c1 4c 40 1d 90 80 e1 07 80 c1 03 38 c1 7c 96
RSP: 0018:ffffc9000057f8f8 EFLAGS: 00010293
RAX: ffffffff844c7a2e RBX: ffff888050100000 RCX: ffff88801ddb0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff844c7a0a R09: 1ffff1100a020035
R10: dffffc0000000000 R11: ffffed100a020036 R12: ffff88803664b300
R13: 1ffff1100a020035 R14: ffff8880501001a8 R15: ffff888050100000
FS: 0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555777f85f8 CR3: 0000000040778000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
bch2_btree_node_rewrite_async+0x3df/0x6a0 fs/bcachefs/btree_update_interior.c:2287
btree_node_read_work+0xf59/0x1260 fs/bcachefs/btree_io.c:1350
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</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@...glegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
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
Powered by blists - more mailing lists