From: syzbot <syzbot+9921e319bd6168140b40@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fuse?] WARNING: refcount bug in process_scheduled_works
Date: Tue, 29 Jul 2025 22:16:03 -0700 [thread overview]
Message-ID: <6889aa93.a00a0220.26d0e1.0019.GAE@google.com> (raw)
In-Reply-To: <20250730020318.3428-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in mddev_put
------------[ cut here ]------------
kernel BUG at drivers/md/md.c:641!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 1 UID: 0 PID: 6615 Comm: syz.0.17 Not tainted 6.16.0-syzkaller-gbeb6c8326eb4-dirty #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:__mddev_put drivers/md/md.c:641 [inline]
RIP: 0010:mddev_put+0x1e9/0x1f0 drivers/md/md.c:660
Code: f9 e9 3f ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 6d ff ff ff 4c 89 f7 e8 12 f3 e0 f9 e9 60 ff ff ff e8 48 e0 7e f9 90 <0f> 0b 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90002ee7cb0 EFLAGS: 00010293
RAX: ffffffff8840dae8 RBX: ffff888033654000 RCX: ffff88802f4bda00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffff888033654133 R09: 1ffff110066ca826
R10: dffffc0000000000 R11: ffffed10066ca827 R12: ffff888027267000
R13: ffff888148c55090 R14: ffff888033654130 R15: dffffc0000000000
FS: 0000555567c20500(0000) GS:ffff888125d86000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000007 CR3: 0000000075a4e000 CR4: 0000000000350ef0
Call Trace:
<TASK>
bdev_release+0x536/0x650 block/bdev.c:-1
blkdev_release+0x15/0x20 block/fops.c:699
__fput+0x44c/0xa70 fs/file_table.c:468
task_work_run+0x1d4/0x260 kernel/task_work.c:227
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop+0xec/0x110 kernel/entry/common.c:43
exit_to_user_mode_prepare include/linux/irq-entry-common.h:208 [inline]
syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline]
do_syscall_64+0x2bd/0x3b0 arch/x86/entry/syscall_64.c:100
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe9c578e9a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007ffe99d6fa48 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 000000000002511a RCX: 00007fe9c578e9a9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007fe9c59b7ba0 R08: 0000000000000001 R09: 0000000899d6fd3f
R10: 00007fe9c5600000 R11: 0000000000000246 R12: 00007fe9c59b5fac
R13: 00007fe9c59b5fa0 R14: ffffffffffffffff R15: 00007ffe99d6fb60
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__mddev_put drivers/md/md.c:641 [inline]
RIP: 0010:mddev_put+0x1e9/0x1f0 drivers/md/md.c:660
Code: f9 e9 3f ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 6d ff ff ff 4c 89 f7 e8 12 f3 e0 f9 e9 60 ff ff ff e8 48 e0 7e f9 90 <0f> 0b 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90002ee7cb0 EFLAGS: 00010293
RAX: ffffffff8840dae8 RBX: ffff888033654000 RCX: ffff88802f4bda00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffff888033654133 R09: 1ffff110066ca826
R10: dffffc0000000000 R11: ffffed10066ca827 R12: ffff888027267000
R13: ffff888148c55090 R14: ffff888033654130 R15: dffffc0000000000
FS: 0000555567c20500(0000) GS:ffff888125d86000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000007 CR3: 0000000075a4e000 CR4: 0000000000350ef0
Tested on:
commit: beb6c832 Merge tag 'uml-for-linux-6.17-rc1' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=152d0834580000
kernel config: https://syzkaller.appspot.com/x/.config?x=dea300d7050f7861
dashboard link: https://syzkaller.appspot.com/bug?extid=9921e319bd6168140b40
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=13a3b1bc580000
next prev parent reply other threads:[~2025-07-30 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:58 [syzbot] [fuse?] WARNING: refcount bug in process_scheduled_works syzbot
2025-07-30 2:03 ` Hillf Danton
2025-07-30 5:16 ` syzbot [this message]
2025-07-30 8:24 ` Hillf Danton
2025-07-30 10:06 ` syzbot
2025-07-30 8:36 ` Hillf Danton
2025-07-30 10:26 ` 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=6889aa93.a00a0220.26d0e1.0019.GAE@google.com \
--to=syzbot+9921e319bd6168140b40@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--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.