Message-ID: <0000000000008b3c4305f0fd4dbe@google.com>
Date:   Thu, 29 Dec 2022 12:26:41 -0800
From:   syzbot <syzbot+49cacf14fd027a089740@...kaller.appspotmail.com>
To:     djwong@...nel.org, linux-kernel@...r.kernel.org,
        linux-xfs@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [xfs?] WARNING in call_rcu (2)

Hello,

syzbot found the following issue on:

HEAD commit:    a5541c0811a0 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=135634a8480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=cbd4e584773e9397
dashboard link: https://syzkaller.appspot.com/bug?extid=49cacf14fd027a089740
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=145749a8480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10bb4118480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4b7702208fb9/disk-a5541c08.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9ec0153ec051/vmlinux-a5541c08.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6f8725ad290a/Image-a5541c08.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ffd09d8cecad/mount_0.gz

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

XFS (loop0): Please unmount the filesystem and rectify the problem(s).
------------[ cut here ]------------
ODEBUG: activate active (active state 1) object type: rcu_head hint: 0x0
WARNING: CPU: 0 PID: 50 at lib/debugobjects.c:505 debug_print_object lib/debugobjects.c:502 [inline]
WARNING: CPU: 0 PID: 50 at lib/debugobjects.c:505 debug_object_activate+0x2c0/0x300 lib/debugobjects.c:674
Modules linked in:
CPU: 0 PID: 50 Comm: kworker/0:1H Not tainted 6.1.0-rc8-syzkaller-33330-ga5541c0811a0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: xfs-log/loop0 xlog_ioend_work
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : debug_print_object lib/debugobjects.c:502 [inline]
pc : debug_object_activate+0x2c0/0x300 lib/debugobjects.c:674
lr : debug_print_object lib/debugobjects.c:502 [inline]
lr : debug_object_activate+0x2c0/0x300 lib/debugobjects.c:674
sp : ffff80000f723880
x29: ffff80000f723880 x28: 0000000000000001 x27: 0000000000000000
x26: 0000000000000000 x25: 0000000000000000 x24: ffff0000c6ad9a50
x23: ffff80000c0cec40 x22: ffff0000c79fcc30 x21: ffff80000f143000
x20: ffff80000c0cec40 x19: ffff0000cab5a638 x18: 00000000000000c0
x17: 6820646165685f75 x16: ffff80000dbe6158 x15: ffff0000c106cec0
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c106cec0
x11: ff808000081c4d64 x10: 0000000000000000 x9 : 41d50f7522bc1100
x8 : 41d50f7522bc1100 x7 : ffff80000c091ebc x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000100000000 x0 : 0000000000000048
Call trace:
 debug_print_object lib/debugobjects.c:502 [inline]
 debug_object_activate+0x2c0/0x300 lib/debugobjects.c:674
 debug_rcu_head_queue kernel/rcu/rcu.h:189 [inline]
 call_rcu+0x40/0x494 kernel/rcu/tree.c:2783
 xfs_buf_rele+0x654/0x780
 xfs_buf_relse fs/xfs/xfs_buf.h:286 [inline]
 xfs_buf_ioend+0x214/0x228 fs/xfs/xfs_buf.c:1339
 xfs_buf_ioend_fail+0x58/0x68 fs/xfs/xfs_buf.c:1397
 xfs_buf_item_unpin+0x18c/0x280 fs/xfs/xfs_buf_item.c:549
 xfs_trans_committed_bulk+0x190/0x460 fs/xfs/xfs_trans.c:806
 xlog_cil_committed+0xcc/0x340 fs/xfs/xfs_log_cil.c:795
 xlog_cil_process_committed+0x6c/0xa8 fs/xfs/xfs_log_cil.c:823
 xlog_state_shutdown_callbacks+0xac/0x140 fs/xfs/xfs_log.c:538
 xlog_force_shutdown+0x1ac/0x230 fs/xfs/xfs_log.c:3821
 xlog_ioend_work+0x68/0xa0 fs/xfs/xfs_log.c:1402
 process_one_work+0x2d8/0x504 kernel/workqueue.c:2289
 worker_thread+0x340/0x610 kernel/workqueue.c:2436
 kthread+0x12c/0x158 kernel/kthread.c:376
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863
irq event stamp: 558
hardirqs last  enabled at (557): [<ffff8000081c3048>] __up_console_sem+0xb0/0xfc kernel/printk/printk.c:261
hardirqs last disabled at (558): [<ffff80000c084084>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last  enabled at (528): [<ffff800008e528b8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (526): [<ffff800008e52884>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
------------[ cut here ]------------
ODEBUG: active_state active (active state 1) object type: rcu_head hint: 0x0
WARNING: CPU: 0 PID: 50 at lib/debugobjects.c:505 debug_print_object lib/debugobjects.c:502 [inline]
WARNING: CPU: 0 PID: 50 at lib/debugobjects.c:505 debug_object_active_state+0x1b0/0x1dc lib/debugobjects.c:950
Modules linked in:
CPU: 0 PID: 50 Comm: kworker/0:1H Tainted: G        W          6.1.0-rc8-syzkaller-33330-ga5541c0811a0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: xfs-log/loop0 xlog_ioend_work
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : debug_print_object lib/debugobjects.c:502 [inline]
pc : debug_object_active_state+0x1b0/0x1dc lib/debugobjects.c:950
lr : debug_print_object lib/debugobjects.c:502 [inline]
lr : debug_object_active_state+0x1b0/0x1dc lib/debugobjects.c:950
sp : ffff80000f723880
x29: ffff80000f723880 x28: 0000000000000001 x27: 0000000000000000
x26: 0000000000000000 x25: 0000000000000000 x24: ffff0000c79fcc30
x23: 0000000000000000 x22: 0000000000000001 x21: ffff80000f10e018
x20: ffff80000c0cec40 x19: ffff80000f143000 x18: 00000000000000c0
x17: 65685f756372203a x16: ffff80000dbe6158 x15: ffff0000c106cec0
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c106cec0
x11: ff808000081c4d64 x10: 0000000000000000 x9 : 41d50f7522bc1100
x8 : 41d50f7522bc1100 x7 : ffff80000c091ebc x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000100000000 x0 : 000000000000004c
Call trace:
 debug_print_object lib/debugobjects.c:502 [inline]
 debug_object_active_state+0x1b0/0x1dc lib/debugobjects.c:950
 debug_rcu_head_queue kernel/rcu/rcu.h:190 [inline]
 call_rcu+0x58/0x494 kernel/rcu/tree.c:2783
 xfs_buf_rele+0x654/0x780
 xfs_buf_relse fs/xfs/xfs_buf.h:286 [inline]
 xfs_buf_ioend+0x214/0x228 fs/xfs/xfs_buf.c:1339
 xfs_buf_ioend_fail+0x58/0x68 fs/xfs/xfs_buf.c:1397
 xfs_buf_item_unpin+0x18c/0x280 fs/xfs/xfs_buf_item.c:549
 xfs_trans_committed_bulk+0x190/0x460 fs/xfs/xfs_trans.c:806
 xlog_cil_committed+0xcc/0x340 fs/xfs/xfs_log_cil.c:795
 xlog_cil_process_committed+0x6c/0xa8 fs/xfs/xfs_log_cil.c:823
 xlog_state_shutdown_callbacks+0xac/0x140 fs/xfs/xfs_log.c:538
 xlog_force_shutdown+0x1ac/0x230 fs/xfs/xfs_log.c:3821
 xlog_ioend_work+0x68/0xa0 fs/xfs/xfs_log.c:1402
 process_one_work+0x2d8/0x504 kernel/workqueue.c:2289
 worker_thread+0x340/0x610 kernel/workqueue.c:2436
 kthread+0x12c/0x158 kernel/kthread.c:376
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863
irq event stamp: 686
hardirqs last  enabled at (685): [<ffff8000081c3048>] __up_console_sem+0xb0/0xfc kernel/printk/printk.c:261
hardirqs last disabled at (686): [<ffff80000c084084>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last  enabled at (658): [<ffff8000080102e4>] _stext+0x2e4/0x37c
softirqs last disabled at (561): [<ffff800008017c88>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:80
---[ end trace 0000000000000000 ]---
rcu: call_rcu(): Double-freed CB 00000000d44ae33c->0x0()!!!   slab xfs_buf start ffff0000cab5a3c0 pointer offset 632


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

Powered by blists - more mailing lists