[syzbot] [reiserfs?] INFO: task hung in queue_log_writer

[syzbot] [reiserfs?] INFO: task hung in queue_log_writer

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    c757fc92a3f7 Merge tag 'spi-fix-v6.2-rc3' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11a3daea480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2b6ecad960fc703e
dashboard link: https://syzkaller.appspot.com/bug?extid=d7c9b7185ced98364b13
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/83ba79e6cb20/disk-c757fc92.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e980be3e55fc/vmlinux-c757fc92.xz
kernel image: https://storage.googleapis.com/syzbot-assets/325d4d480267/bzImage-c757fc92.xz

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

INFO: task kworker/u4:11:5357 blocked for more than 143 seconds.
      Not tainted 6.2.0-rc3-syzkaller-00060-gc757fc92a3f7 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:11   state:D stack:26224 pid:5357  ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:1)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 queue_log_writer+0x293/0x2f0 fs/reiserfs/journal.c:2980
 do_journal_begin_r+0x988/0x10e0 fs/reiserfs/journal.c:3103
 journal_begin+0x166/0x400 fs/reiserfs/journal.c:3255
 reiserfs_write_inode+0x1f4/0x2d0 fs/reiserfs/inode.c:1777
 write_inode fs/fs-writeback.c:1451 [inline]
 __writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1663
 writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1889
 wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2063
 wb_do_writeback fs/fs-writeback.c:2206 [inline]
 wb_workfn+0x2e0/0x12f0 fs/fs-writeback.c:2246
 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
 worker_thread+0x669/0x1090 kernel/workqueue.c:2436
 kthread+0x2e8/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
INFO: task syz-executor.1:5768 blocked for more than 143 seconds.
      Not tainted 6.2.0-rc3-syzkaller-00060-gc757fc92a3f7 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:24760 pid:5768  ppid:5109   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 bit_wait+0x16/0xe0 kernel/sched/wait_bit.c:199
 __wait_on_bit+0x64/0x180 kernel/sched/wait_bit.c:49
 __inode_wait_for_writeback+0x153/0x1f0 fs/fs-writeback.c:1472
 inode_wait_for_writeback+0x26/0x40 fs/fs-writeback.c:1484
 evict+0x2b7/0x6b0 fs/inode.c:661
 iput_final fs/inode.c:1747 [inline]
 iput.part.0+0x59b/0x880 fs/inode.c:1773
 iput+0x5c/0x80 fs/inode.c:1763
 dentry_unlink_inode+0x2b1/0x460 fs/dcache.c:401
 d_delete fs/dcache.c:2565 [inline]
 d_delete+0x16f/0x1c0 fs/dcache.c:2554
 xattr_unlink+0x139/0x190 fs/reiserfs/xattr.c:96
 lookup_and_delete_xattr fs/reiserfs/xattr.c:494 [inline]
 reiserfs_xattr_set_handle+0x83c/0xb00 fs/reiserfs/xattr.c:529
 reiserfs_xattr_set+0x454/0x5b0 fs/reiserfs/xattr.c:633
 trusted_set+0xa7/0xd0 fs/reiserfs/xattr_trusted.c:31
 __vfs_removexattr+0x155/0x1c0 fs/xattr.c:497
 __vfs_removexattr_locked+0x1b0/0x440 fs/xattr.c:532
 vfs_removexattr+0xcf/0x260 fs/xattr.c:554
 ovl_do_removexattr fs/overlayfs/overlayfs.h:272 [inline]
 ovl_removexattr fs/overlayfs/overlayfs.h:280 [inline]
 ovl_make_workdir fs/overlayfs/super.c:1361 [inline]
 ovl_get_workdir fs/overlayfs/super.c:1444 [inline]
 ovl_fill_super+0x20ba/0x6330 fs/overlayfs/super.c:2000
 mount_nodev+0x64/0x120 fs/super.c:1405
 legacy_get_tree+0x109/0x220 fs/fs_context.c:610
 vfs_get_tree+0x8d/0x2f0 fs/super.c:1489
 do_new_mount fs/namespace.c:3145 [inline]
 path_mount+0x132a/0x1e20 fs/namespace.c:3475
 do_mount fs/namespace.c:3488 [inline]
 __do_sys_mount fs/namespace.c:3697 [inline]
 __se_sys_mount fs/namespace.c:3674 [inline]
 __x64_sys_mount+0x283/0x300 fs/namespace.c:3674
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff5f6c8c0c9
RSP: 002b:00007ff5f7993168 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ff5f6dabf80 RCX: 00007ff5f6c8c0c9
RDX: 0000000020000080 RSI: 00000000200000c0 RDI: 0000000000000000
RBP: 00007ff5f6ce7ae9 R08: 0000000020000480 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd299fb68f R14: 00007ff5f7993300 R15: 0000000000022000
 </TASK>
INFO: task syz-executor.1:5787 blocked for more than 144 seconds.
      Not tainted 6.2.0-rc3-syzkaller-00060-gc757fc92a3f7 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:26120 pid:5787  ppid:5109   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 wb_wait_for_completion+0x182/0x240 fs/fs-writeback.c:192
 sync_inodes_sb+0x1aa/0x9e0 fs/fs-writeback.c:2725
 sync_filesystem.part.0+0xe6/0x1d0 fs/sync.c:64
 sync_filesystem+0x8f/0xc0 fs/sync.c:43
 reiserfs_remount+0x129/0x1540 fs/reiserfs/super.c:1445
 legacy_reconfigure+0x119/0x180 fs/fs_context.c:633
 reconfigure_super+0x40c/0xa30 fs/super.c:935
 do_remount fs/namespace.c:2807 [inline]
 path_mount+0x1830/0x1e20 fs/namespace.c:3467
 do_mount fs/namespace.c:3488 [inline]
 __do_sys_mount fs/namespace.c:3697 [inline]
 __se_sys_mount fs/namespace.c:3674 [inline]
 __x64_sys_mount+0x283/0x300 fs/namespace.c:3674
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff5f6c8d5fa
RSP: 002b:00007ff5f7971f88 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff5f6c8d5fa
RDX: 00000000200000c0 RSI: 0000000020000100 RDI: 0000000000000000
RBP: 00007ff5f7972020 R08: 00007ff5f7972020 R09: 0000000001a484bc
R10: 0000000001a484bc R11: 0000000000000206 R12: 00000000200000c0
R13: 0000000020000100 R14: 00007ff5f7971fe0 R15: 00000000200007c0
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8c790f30 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8c790c30 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
1 lock held by khungtaskd/28:
 #0: ffffffff8c791a80 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x57/0x264 kernel/locking/lockdep.c:6494
5 locks held by kworker/u4:3/46:
 #0: ffff8880b983b598 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2f/0x120 kernel/sched/core.c:537
 #1: ffff8880b98287c8 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x2de/0x930 kernel/sched/psi.c:976
 #2: ffff8880b9829618 (&base->lock){-.-.}-{2:2}, at: lock_timer_base+0x5a/0x1f0 kernel/time/timer.c:999
 #3: ffffffff91dee210 (&obj_hash[i].lock){-.-.}-{2:2}, at: debug_object_activate+0x132/0x3e0 lib/debugobjects.c:665
 #4: ffff8880b98293f0 (krc.lock){..-.}-{2:2}, at: krc_this_cpu_lock kernel/rcu/tree.c:2977 [inline]
 #4: ffff8880b98293f0 (krc.lock){..-.}-{2:2}, at: add_ptr_to_bulk_krc_lock kernel/rcu/tree.c:3286 [inline]
 #4: ffff8880b98293f0 (krc.lock){..-.}-{2:2}, at: kvfree_call_rcu+0xe2/0x8f0 kernel/rcu/tree.c:3377
2 locks held by getty/4747:
 #0: ffff88802baab098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x26/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffffc900015b02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef4/0x13e0 drivers/tty/n_tty.c:2177
2 locks held by kworker/u4:11/5357:
 #0: ffff888140858138 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888140858138 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888140858138 ((wq_completion)writeback){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1280 [inline]
 #0: ffff888140858138 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:636 [inline]
 #0: ffff888140858138 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:663 [inline]
 #0: ffff888140858138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x86d/0x1710 kernel/workqueue.c:2260
 #1: ffffc90005117da8 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x8a1/0x1710 kernel/workqueue.c:2264
4 locks held by syz-executor.1/5768:
 #0: ffff88807b9320e0 (&type->s_umount_key#47/1){+.+.}-{3:3}, at: alloc_super+0x22e/0xb60 fs/super.c:228
 #1: ffff88807c650460 (sb_writers#15){.+.+}-{0:0}, at: ovl_make_workdir fs/overlayfs/super.c:1290 [inline]
 #1: ffff88807c650460 (sb_writers#15){.+.+}-{0:0}, at: ovl_get_workdir fs/overlayfs/super.c:1444 [inline]
 #1: ffff88807c650460 (sb_writers#15){.+.+}-{0:0}, at: ovl_fill_super+0x19d6/0x6330 fs/overlayfs/super.c:2000
 #2: ffff88807332e640 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
 #2: ffff88807332e640 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: vfs_removexattr+0xbb/0x260 fs/xattr.c:553
 #3: ffff88808791dfa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
 #3: ffff88808791dfa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: lookup_and_delete_xattr fs/reiserfs/xattr.c:486 [inline]
 #3: ffff88808791dfa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: reiserfs_xattr_set_handle+0x7ab/0xb00 fs/reiserfs/xattr.c:529
2 locks held by syz-executor.1/5787:
 #0: ffff88807c6500e0 (&type->s_umount_key#53){++++}-{3:3}, at: do_remount fs/namespace.c:2804 [inline]
 #0: ffff88807c6500e0 (&type->s_umount_key#53){++++}-{3:3}, at: path_mount+0x13e0/0x1e20 fs/namespace.c:3467
 #1: ffff88801e4b27d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline]
 #1: ffff88801e4b27d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x190/0x9e0 fs/fs-writeback.c:2723
2 locks held by kworker/u4:14/8107:
 #0: ffff8880b983b598 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2f/0x120 kernel/sched/core.c:537
 #1: ffff8880b98287c8 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x216/0x930 kernel/sched/psi.c:964
1 lock held by syz-executor.5/8770:
 #0: ffff88807c6500e0 (&type->s_umount_key#53){++++}-{3:3}, at: iterate_supers+0xdf/0x2a0 fs/super.c:722

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.2.0-rc3-syzkaller-00060-gc757fc92a3f7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106
 nmi_cpu_backtrace.cold+0x24/0x18a lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x333/0x3c0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
 watchdog+0xc75/0xfc0 kernel/hung_task.c:377
 kthread+0x2e8/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8154 Comm: kworker/u4:16 Not tainted 6.2.0-rc3-syzkaller-00060-gc757fc92a3f7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: phy4 ieee80211_iface_work
RIP: 0010:virt_to_folio include/linux/mm.h:958 [inline]
RIP: 0010:virt_to_slab mm/slab.h:185 [inline]
RIP: 0010:kmem_cache_free+0x6b/0x5c0 mm/slub.c:3809
Code: 8b 05 45 9b 34 7e 3b 05 f3 c6 a3 0c 0f 83 bf 02 00 00 89 c0 48 0f a3 05 f3 c4 a3 0c 0f 82 45 02 00 00 48 89 df 4c 8b 6c 24 60 <e8> 60 66 6a ff 48 c1 e8 0c 49 89 c4 48 b8 00 00 00 00 00 ea ff ff
RSP: 0018:ffffc9001477fbf0 EFLAGS: 00000286
RAX: 0000000000000001 RBX: ffff88807dd51780 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88807dd51780
RBP: ffff88801271e280 R08: 0000000000000001 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000094001 R12: 0000000000000000
R13: ffffffff87c1e69f R14: ffffffff8945abc7 R15: ffff888025de5878
FS:  0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c00f8e7000 CR3: 0000000020d2d000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 kfree_skbmem+0xef/0x1b0 net/core/skbuff.c:874
 __kfree_skb net/core/skbuff.c:931 [inline]
 kfree_skb_reason+0x1b8/0x4f0 net/core/skbuff.c:956
 kfree_skb include/linux/skbuff.h:1218 [inline]
 ieee80211_iface_work+0x357/0xd70 net/mac80211/iface.c:1637
 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
 worker_thread+0x669/0x1090 kernel/workqueue.c:2436
 kthread+0x2e8/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </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@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Re: [syzbot] [reiserfs?] INFO: task hung in queue_log_writer

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit:    c8c655c34e33 Merge tag 'for-linus' of git://git.kernel.org..
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12c9db44280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d56ffc213bf6bf4a
dashboard link: https://syzkaller.appspot.com/bug?extid=d7c9b7185ced98364b13
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=118645f8280000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17bce9d8280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b41434707a6f/disk-c8c655c3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3051545315a4/vmlinux-c8c655c3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/924dba1778d0/bzImage-c8c655c3.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/c6297f191793/mount_0.gz

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

INFO: task kworker/u4:5:2412 blocked for more than 143 seconds.
      Not tainted 6.3.0-syzkaller-12378-gc8c655c34e33 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:5    state:D stack:23832 pid:2412  ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:5)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 queue_log_writer+0x293/0x2f0 fs/reiserfs/journal.c:2980
 do_journal_begin_r+0x988/0x10e0 fs/reiserfs/journal.c:3101
 journal_begin+0x166/0x400 fs/reiserfs/journal.c:3253
 reiserfs_write_inode+0x1f4/0x2d0 fs/reiserfs/inode.c:1777
 write_inode fs/fs-writeback.c:1456 [inline]
 __writeback_single_inode+0x9f2/0xdb0 fs/fs-writeback.c:1668
 writeback_sb_inodes+0x54d/0xe70 fs/fs-writeback.c:1894
 wb_writeback+0x294/0xa50 fs/fs-writeback.c:2068
 wb_do_writeback fs/fs-writeback.c:2211 [inline]
 wb_workfn+0x2a5/0xfc0 fs/fs-writeback.c:2251
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2405
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2552
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
INFO: task syz-executor302:5808 blocked for more than 144 seconds.
      Not tainted 6.3.0-syzkaller-12378-gc8c655c34e33 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor302 state:D stack:24728 pid:5808  ppid:5003   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 bit_wait+0x16/0xe0 kernel/sched/wait_bit.c:199
 __wait_on_bit+0x64/0x180 kernel/sched/wait_bit.c:49
 __inode_wait_for_writeback+0x153/0x1f0 fs/fs-writeback.c:1477
 inode_wait_for_writeback+0x26/0x40 fs/fs-writeback.c:1489
 evict+0x2b7/0x6b0 fs/inode.c:662
 iput_final fs/inode.c:1747 [inline]
 iput.part.0+0x50a/0x740 fs/inode.c:1773
 iput+0x5c/0x80 fs/inode.c:1763
 dentry_unlink_inode+0x2b1/0x460 fs/dcache.c:401
 d_delete fs/dcache.c:2565 [inline]
 d_delete+0x16f/0x1c0 fs/dcache.c:2554
 xattr_unlink+0x139/0x190 fs/reiserfs/xattr.c:97
 lookup_and_delete_xattr fs/reiserfs/xattr.c:495 [inline]
 reiserfs_xattr_set_handle+0x7bd/0xb00 fs/reiserfs/xattr.c:530
 reiserfs_xattr_set+0x454/0x5b0 fs/reiserfs/xattr.c:634
 trusted_set+0xa7/0xd0 fs/reiserfs/xattr_trusted.c:31
 __vfs_removexattr+0x155/0x1c0 fs/xattr.c:519
 __vfs_removexattr_locked+0x1b0/0x440 fs/xattr.c:554
 vfs_removexattr+0xcf/0x260 fs/xattr.c:576
 ovl_do_removexattr fs/overlayfs/overlayfs.h:273 [inline]
 ovl_removexattr fs/overlayfs/overlayfs.h:281 [inline]
 ovl_make_workdir fs/overlayfs/super.c:1353 [inline]
 ovl_get_workdir fs/overlayfs/super.c:1436 [inline]
 ovl_fill_super+0x6ec5/0x7270 fs/overlayfs/super.c:1992
 mount_nodev+0x64/0x120 fs/super.c:1426
 legacy_get_tree+0x109/0x220 fs/fs_context.c:610
 vfs_get_tree+0x8d/0x350 fs/super.c:1510
 do_new_mount fs/namespace.c:3039 [inline]
 path_mount+0x134b/0x1e40 fs/namespace.c:3369
 do_mount fs/namespace.c:3382 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x283/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6a58a51f39
RSP: 002b:00007f6a589f5208 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f6a58ad0768 RCX: 00007f6a58a51f39
RDX: 0000000020000080 RSI: 00000000200000c0 RDI: 0000000000000000
RBP: 00007f6a58ad0760 R08: 0000000020000480 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6a58ad076c
R13: 00007ffc3484baef R14: 00007f6a589f5300 R15: 0000000000022000
 </TASK>
INFO: task syz-executor302:5819 blocked for more than 144 seconds.
      Not tainted 6.3.0-syzkaller-12378-gc8c655c34e33 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor302 state:D stack:28496 pid:5819  ppid:5003   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 wb_wait_for_completion+0x182/0x240 fs/fs-writeback.c:192
 sync_inodes_sb+0x1aa/0xa60 fs/fs-writeback.c:2730
 sync_filesystem.part.0+0xe6/0x1d0 fs/sync.c:64
 sync_filesystem+0x8f/0xc0 fs/sync.c:43
 reiserfs_remount+0x129/0x1650 fs/reiserfs/super.c:1445
 legacy_reconfigure+0x119/0x180 fs/fs_context.c:633
 reconfigure_super+0x40c/0xa30 fs/super.c:956
 do_remount fs/namespace.c:2701 [inline]
 path_mount+0x1846/0x1e40 fs/namespace.c:3361
 do_mount fs/namespace.c:3382 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x283/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6a58a533fa
RSP: 002b:00007f6a509d4028 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f6a509d46b8 RCX: 00007f6a58a533fa
RDX: 00000000200001c0 RSI: 0000000020000100 RDI: 0000000000000000
RBP: 00000000ffffffff R08: 00007f6a509d40c0 R09: 0000000000000000
R10: 0000000001a484bc R11: 0000000000000286 R12: 00000000200001c0
R13: 0000000020000100 R14: 0000000000000000 R15: 00000000200004c0
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8c798630 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:518
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8c798330 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:518
1 lock held by khungtaskd/28:
 #0: ffffffff8c799240 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x340 kernel/locking/lockdep.c:6545
2 locks held by kworker/u4:4/58:
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2376
 #1: ffffc90001577db0 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2380
2 locks held by kworker/0:2/894:
 #0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2376
 #1: ffffc90004cdfdb0 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2380
2 locks held by kworker/u4:5/2412:
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff888141a53938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2376
 #1: ffffc9000a3a7db0 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2380
2 locks held by getty/4753:
 #0: ffff888027e54098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x26/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015902f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef4/0x13e0 drivers/tty/n_tty.c:2176
1 lock held by syz-executor302/4997:
 #0: ffff88802b0620e0 (&type->s_umount_key#42){+.+.}-{3:3}, at: deactivate_super+0xa9/0xd0 fs/super.c:361
2 locks held by syz-executor302/4998:
 #0: ffff88806f9ce0e0 (&type->s_umount_key#42){+.+.}-{3:3}, at: deactivate_super+0xa9/0xd0 fs/super.c:361
 #1: ffffffff8c7a46b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:325 [inline]
 #1: ffffffff8c7a46b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3e8/0x770 kernel/rcu/tree_exp.h:992
2 locks held by syz-executor302/5000:
 #0: ffff8880193da0e0 (&type->s_umount_key#42){+.+.}-{3:3}, at: deactivate_super+0xa9/0xd0 fs/super.c:361
 #1: ffffffff8c7a46b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:293 [inline]
 #1: ffffffff8c7a46b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x64a/0x770 kernel/rcu/tree_exp.h:992
1 lock held by syz-executor302/5001:
 #0: ffff88807704c0e0 (&type->s_umount_key#42){+.+.}-{3:3}, at: deactivate_super+0xa9/0xd0 fs/super.c:361
4 locks held by syz-executor302/5808:
 #0: ffff88807a3400e0 (&type->s_umount_key#41/1){+.+.}-{3:3}, at: alloc_super+0x22e/0xb60 fs/super.c:228
 #1: ffff888076d4e460 (sb_writers#10){.+.+}-{0:0}, at: ovl_make_workdir fs/overlayfs/super.c:1282 [inline]
 #1: ffff888076d4e460 (sb_writers#10){.+.+}-{0:0}, at: ovl_get_workdir fs/overlayfs/super.c:1436 [inline]
 #1: ffff888076d4e460 (sb_writers#10){.+.+}-{0:0}, at: ovl_fill_super+0x1c5e/0x7270 fs/overlayfs/super.c:1992
 #2: ffff888073b1ece0 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #2: ffff888073b1ece0 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: vfs_removexattr+0xbb/0x260 fs/xattr.c:575
 #3: ffff888073adbe80 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:810 [inline]
 #3: ffff888073adbe80 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: lookup_and_delete_xattr fs/reiserfs/xattr.c:487 [inline]
 #3: ffff888073adbe80 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: reiserfs_xattr_set_handle+0x72c/0xb00 fs/reiserfs/xattr.c:530
2 locks held by syz-executor302/5819:
 #0: ffff888076d4e0e0 (&type->s_umount_key#42){+.+.}-{3:3}, at: do_remount fs/namespace.c:2698 [inline]
 #0: ffff888076d4e0e0 (&type->s_umount_key#42){+.+.}-{3:3}, at: path_mount+0x1401/0x1e40 fs/namespace.c:3361
 #1: ffff88801ee6c7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline]
 #1: ffff88801ee6c7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x190/0xa60 fs/fs-writeback.c:2728
4 locks held by syz-executor302/6995:
 #0: ffff88807dc2c0e0 (&type->s_umount_key#41/1){+.+.}-{3:3}, at: alloc_super+0x22e/0xb60 fs/super.c:228
 #1: ffff88807c150460 (sb_writers#10){.+.+}-{0:0}, at: ovl_make_workdir fs/overlayfs/super.c:1282 [inline]
 #1: ffff88807c150460 (sb_writers#10){.+.+}-{0:0}, at: ovl_get_workdir fs/overlayfs/super.c:1436 [inline]
 #1: ffff88807c150460 (sb_writers#10){.+.+}-{0:0}, at: ovl_fill_super+0x1c5e/0x7270 fs/overlayfs/super.c:1992
 #2: ffff8880739cc520 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #2: ffff8880739cc520 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: vfs_removexattr+0xbb/0x260 fs/xattr.c:575
 #3: ffff88807390d260 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:810 [inline]
 #3: ffff88807390d260 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: lookup_and_delete_xattr fs/reiserfs/xattr.c:487 [inline]
 #3: ffff88807390d260 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: reiserfs_xattr_set_handle+0x72c/0xb00 fs/reiserfs/xattr.c:530
2 locks held by syz-executor302/7005:
 #0: ffff88807c1500e0 (&type->s_umount_key#42){+.+.}-{3:3}, at: do_remount fs/namespace.c:2698 [inline]
 #0: ffff88807c1500e0 (&type->s_umount_key#42){+.+.}-{3:3}, at: path_mount+0x1401/0x1e40 fs/namespace.c:3361
 #1: ffff8881417e27d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline]
 #1: ffff8881417e27d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x190/0xa60 fs/fs-writeback.c:2728

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.3.0-syzkaller-12378-gc8c655c34e33 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x29c/0x350 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x2a4/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xe16/0x1090 kernel/hung_task.c:379
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 894 Comm: kworker/0:2 Not tainted 6.3.0-syzkaller-12378-gc8c655c34e33 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Workqueue: rcu_gp process_srcu
RIP: 0010:do_raw_spin_lock+0x1ac/0x2b0 kernel/locking/spinlock_debug.c:118
Code: 03 65 4c 8b 24 25 c0 bb 03 00 80 3c 02 00 0f 85 e3 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 65 10 48 c7 04 03 00 00 00 00 <48> 8b 44 24 60 65 48 2b 04 25 28 00 00 00 0f 85 c6 00 00 00 48 83
RSP: 0018:ffffc90004cdfa80 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: 1ffff9200099bf51 RCX: ffffffff81666574
RDX: 1ffffffff23f75a2 RSI: 0000000000000004 RDI: ffffc90004cdfaa8
RBP: ffffffff91fbad00 R08: 0000000000000001 R09: 0000000000000003
R10: fffff5200099bf55 R11: 0000000000000000 R12: ffff88801f738000
R13: ffffffff91fbad10 R14: 0000000000000000 R15: 1ffff9200099bf6a
FS:  0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6a509d4718 CR3: 000000000c571000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:111 [inline]
 _raw_spin_lock_irqsave+0x45/0x60 kernel/locking/spinlock.c:162
 debug_object_activate+0x134/0x3f0 lib/debugobjects.c:690
 debug_work_activate kernel/workqueue.c:517 [inline]
 __queue_work+0x614/0x1120 kernel/workqueue.c:1525
 __queue_delayed_work+0x1c8/0x270 kernel/workqueue.c:1674
 queue_delayed_work_on+0x109/0x120 kernel/workqueue.c:1710
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2405
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2552
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </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.