All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e7b9dfa79acffd3aabdd@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in bch2_trans_update_by_path (2)
Date: Thu, 25 Sep 2025 03:26:27 -0700	[thread overview]
Message-ID: <68d518d3.050a0220.3a612a.0009.GAE@google.com> (raw)
In-Reply-To: <68c3c675.050a0220.2ff435.0354.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    0f3be52b8e37 Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=15205ce2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=714d45b6135c308e
dashboard link: https://syzkaller.appspot.com/bug?extid=e7b9dfa79acffd3aabdd
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=123cace2580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1374e142580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a2c3b345c3da/disk-0f3be52b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/54368457365a/vmlinux-0f3be52b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3544cf9b3f24/Image-0f3be52b.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/09727f6cbd01/mount_0.gz

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

bcachefs (loop0): pointer to missing indirect extent in (disconnected) offset 0: -12288
  u64s 7 type reflink_p 4102:24:U32_MAX len 24 ver 0: idx 0 front_pad 0 back_pad 0
  missing reflink btree range 0-24, fixing
------------[ cut here ]------------
kernel BUG at fs/bcachefs/btree_update.c:410!
Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP
Modules linked in:
CPU: 0 UID: 0 PID: 6643 Comm: syz-executor Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : bch2_trans_update_by_path+0x17ec/0x17f0 fs/bcachefs/btree_update.c:410
lr : bch2_trans_update_by_path+0x17ec/0x17f0 fs/bcachefs/btree_update.c:410
sp : ffff8000a10661c0
x29: ffff8000a1066380 x28: 0000000000000004 x27: ffff0000c83cc000
x26: 0000000000000000 x25: ffff0000d6c81268 x24: 1fffe00019079802
x23: 0000000000000000 x22: ffff0000c83ce4d8 x21: 0000000000004000
x20: dfff800000000000 x19: ffff0000c83ce4d8 x18: 00000000ffffffff
x17: 3233553a303a3230 x16: ffff80008af86288 x15: 0000000000000003
x14: 0000000000000000 x13: 0000000000000006 x12: 0000000000ff0100
x11: ffff0000d33bbd00 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000d33bbd00 x7 : 0000100600000000 x6 : ffff800082901c6c
x5 : 0000000000000812 x4 : ffff8000828fcb24 x3 : 0000000000100000
x2 : ffff0000d6c81268 x1 : 0000000000004000 x0 : 0000000000000000
Call trace:
 bch2_trans_update_by_path+0x17ec/0x17f0 fs/bcachefs/btree_update.c:410 (P)
 bch2_trans_update_ip+0x7bc/0x17ec fs/bcachefs/btree_update.c:531
 bch2_trans_update+0x4c/0x60 fs/bcachefs/btree_update.h:123
 bch2_btree_insert_nonextent fs/bcachefs/btree_update.c:625 [inline]
 bch2_trans_update_extent fs/bcachefs/btree_update.c:321 [inline]
 bch2_trans_update_ip+0x1320/0x17ec fs/bcachefs/btree_update.c:503
 bch2_trans_update+0x4c/0x60 fs/bcachefs/btree_update.h:123
 bch2_btree_insert_trans+0x180/0x2a8 fs/bcachefs/btree_update.c:637
 bch2_indirect_extent_missing_error+0x778/0xafc fs/bcachefs/reflink.c:239
 bch2_lookup_indirect_extent+0x334/0x558 fs/bcachefs/reflink.c:279
 trans_trigger_reflink_p_segment fs/bcachefs/reflink.c:308 [inline]
 __trigger_reflink_p+0x270/0xf40 fs/bcachefs/reflink.c:419
 bch2_trigger_reflink_p+0x114/0x244 fs/bcachefs/reflink.c:454
 run_one_trans_trigger fs/bcachefs/btree_trans_commit.c:-1 [inline]
 bch2_trans_commit_run_triggers fs/bcachefs/btree_trans_commit.c:554 [inline]
 __bch2_trans_commit+0x800/0x625c fs/bcachefs/btree_trans_commit.c:1023
 bch2_trans_commit fs/bcachefs/btree_update.h:241 [inline]
 bch2_inode_delete_keys+0x3d8/0x584 fs/bcachefs/inode.c:1115
 bch2_inode_rm+0x214/0x4e0 fs/bcachefs/inode.c:1146
 bch2_evict_inode+0x1b4/0x444 fs/bcachefs/fs.c:2182
 evict+0x414/0x928 fs/inode.c:810
 iput_final fs/inode.c:1897 [inline]
 iput+0x6e4/0x83c fs/inode.c:1923
 do_unlinkat+0x300/0x488 fs/namei.c:4657
 __do_sys_unlinkat fs/namei.c:4691 [inline]
 __se_sys_unlinkat fs/namei.c:4684 [inline]
 __arm64_sys_unlinkat+0xdc/0xf8 fs/namei.c:4684
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x5c/0x254 arch/arm64/kernel/entry-common.c:744
 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:763
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
Code: d4210000 9778c3b9 d4210000 9778c3b7 (d4210000) 
---[ end trace 0000000000000000 ]---


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

      reply	other threads:[~2025-09-25 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12  7:06 [syzbot] [bcachefs?] kernel BUG in bch2_trans_update_by_path (2) syzbot
2025-09-25 10:26 ` syzbot [this message]

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=68d518d3.050a0220.3a612a.0009.GAE@google.com \
    --to=syzbot+e7b9dfa79acffd3aabdd@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.