[v6.1] INFO: task hung in gfs2_gl_hash_clear

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1321ab403b38 Linux 6.1.45
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e78553a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=98e020fdb0f6ab0f
dashboard link: https://syzkaller.appspot.com/bug?extid=84d611282adb63889ac8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14a09b73a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13853037a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3b9d65a68f82/disk-1321ab40.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/afca87deee2c/vmlinux-1321ab40.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c93e18288863/Image-1321ab40.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9a3bc61500c6/mount_0.gz

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

INFO: task syz-executor282:4260 blocked for more than 143 seconds.
Not tainted 6.1.45-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor282 state:D stack:0 pid:4260 ppid:4258 flags:0x00000004
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6554
schedule+0xc4/0x170 kernel/sched/core.c:6630
schedule_timeout+0x1d8/0x344 kernel/time/timer.c:1935
gfs2_gl_hash_clear+0x178/0x2e0 fs/gfs2/glock.c:2265
gfs2_put_super+0x640/0x6d4 fs/gfs2/super.c:625
generic_shutdown_super+0x130/0x328 fs/super.c:501
kill_block_super+0x70/0xdc fs/super.c:1459
gfs2_kill_sb+0xc0/0xd4
deactivate_locked_super+0xac/0x124 fs/super.c:332
deactivate_super+0xf0/0x110 fs/super.c:363
cleanup_mnt+0x394/0x41c fs/namespace.c:1186
__cleanup_mnt+0x20/0x30 fs/namespace.c:1193
task_work_run+0x240/0x2f0 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2144/0x3470 arch/arm64/kernel/signal.c:1132
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x168 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015a74ef0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff800015a756f0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffff800015a74d20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3983:
#0: ffff0000d6306098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bd102f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
1 lock held by syz-executor282/4260:
#0: ffff0000ddf6e0e0 (&type->s_umount_key#40){+.+.}-{3:3}, at: deactivate_super+0xe8/0x110 fs/super.c:362

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



---
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 syzk...@googlegroups.com.

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

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit 71733b4922007500ae259af9e96017080f5d36d9
git tree: upstream
Author: Edward Adam Davis <ead...@qq.com>
Date: Sat Dec 2 09:25:49 2023 +0000

gfs2: fix kernel BUG in gfs2_quota_cleanup

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=170e53d7e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=641b679746d8a982
dashboard link: https://syzkaller.appspot.com/bug?extid=84d611282adb63889ac8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101807abe80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14ac70e3e80000


Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection