public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+08d08d52c3a09bfc70f7@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?] WARNING in bch2_fs_release
Date: Sat, 08 Feb 2025 16:19:29 -0800	[thread overview]
Message-ID: <67a7f491.050a0220.3d72c.0031.GAE@google.com> (raw)
In-Reply-To: <66f01abe.050a0220.3195df.009d.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    8f6629c004b1 kbuild: Move -Wenum-enum-conversion to W=2
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12b102a4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=147b7d49d83b8036
dashboard link: https://syzkaller.appspot.com/bug?extid=08d08d52c3a09bfc70f7
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=1312cbdf980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=129411b0580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f60addb0f276/disk-8f6629c0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/59d0658fa6fd/vmlinux-8f6629c0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25afa4128fc2/bzImage-8f6629c0.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/574abc7822e2/mount_0.gz

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

bcachefs (loop0): shutting down
bcachefs (loop0): shutdown complete
------------[ cut here ]------------
online_reserved not 0 at shutdown: 1792
WARNING: CPU: 0 PID: 5820 at fs/bcachefs/super.c:585 __bch2_fs_free fs/bcachefs/super.c:585 [inline]
WARNING: CPU: 0 PID: 5820 at fs/bcachefs/super.c:585 bch2_fs_release+0x744/0x7b0 fs/bcachefs/super.c:624
Modules linked in:
CPU: 0 UID: 0 PID: 5820 Comm: syz-executor117 Not tainted 6.14.0-rc1-syzkaller-00187-g8f6629c004b1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:__bch2_fs_free fs/bcachefs/super.c:585 [inline]
RIP: 0010:bch2_fs_release+0x744/0x7b0 fs/bcachefs/super.c:624
Code: 41 5e 41 5f 5d e9 2c 67 33 fd e8 37 85 49 fd e9 06 fd ff ff e8 2d 85 49 fd 90 48 c7 c7 a0 6a 55 8c 4c 89 ee e8 fd 2f 0a fd 90 <0f> 0b 90 90 e9 13 fd ff ff 44 89 f1 80 e1 07 38 c1 0f 8c 18 fb ff
RSP: 0018:ffffc90003e2fb88 EFLAGS: 00010246
RAX: c22db852ba485a00 RBX: ffff888077104a10 RCX: ffff88807de41e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 1ffff1100ee20942 R08: ffffffff81800b32 R09: 1ffff110170c519a
R10: dffffc0000000000 R11: ffffed10170c519b R12: 00000000fffffff8
R13: 0000000000000700 R14: dffffc0000000000 R15: 0000607f47622c00
FS:  000055555c502380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff51ad82bc CR3: 00000000781b8000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 kobject_cleanup lib/kobject.c:689 [inline]
 kobject_release lib/kobject.c:720 [inline]
 kref_put include/linux/kref.h:65 [inline]
 kobject_put+0x22f/0x480 lib/kobject.c:737
 deactivate_locked_super+0xc4/0x130 fs/super.c:473
 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1413
 task_work_run+0x24f/0x310 kernel/task_work.c:227
 ptrace_notify+0x2d2/0x380 kernel/signal.c:2522
 ptrace_report_syscall include/linux/ptrace.h:415 [inline]
 ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]
 syscall_exit_work+0xc7/0x1d0 kernel/entry/common.c:173
 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]
 syscall_exit_to_user_mode+0x24a/0x340 kernel/entry/common.c:218
 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8aac0ec447
Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007fff51ad82a8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f8aac0ec447
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff51ad8360
RBP: 00007fff51ad8360 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000202 R12: 00007fff51ad93d0
R13: 000055555c5036c0 R14: 0000000000000001 R15: 431bde82d7b634db
 </TASK>


---
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-02-09  0:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 13:25 [syzbot] [bcachefs?] WARNING in bch2_fs_release syzbot
2025-02-09  0:19 ` syzbot [this message]
2025-02-09 19:27 ` syzbot
2025-05-09 11:46 ` 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=67a7f491.050a0220.3d72c.0031.GAE@google.com \
    --to=syzbot+08d08d52c3a09bfc70f7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox