[v6.1] INFO: task hung in gfs2_glock_nq

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bf1e3b1cb1e0 Linux 6.1.85
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10415d9d180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c45aa0208e0ade9
dashboard link: https://syzkaller.appspot.com/bug?extid=90f9c53a8e1181aa3f4b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b5845a33eff1/disk-bf1e3b1c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/78ce74185067/vmlinux-bf1e3b1c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b63c759797bf/Image-bf1e3b1c.gz.xz

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

INFO: task syz-executor.2:4251 blocked for more than 143 seconds.
Not tainted 6.1.85-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:0 pid:4251 ppid:1 flags:0x00000005
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
bit_wait+0x1c/0xac kernel/sched/wait_bit.c:199
__wait_on_bit kernel/sched/wait_bit.c:49 [inline]
out_of_line_wait_on_bit+0x208/0x334 kernel/sched/wait_bit.c:64
wait_on_bit include/linux/wait_bit.h:76 [inline]
gfs2_glock_wait+0xb8/0x298 fs/gfs2/glock.c:1346
gfs2_glock_nq+0x940/0x13d8 fs/gfs2/glock.c:1598
gfs2_glock_nq_init fs/gfs2/glock.h:264 [inline]
__gfs2_lookup+0x140/0x28c fs/gfs2/inode.c:879
gfs2_lookup+0x2c/0x3c fs/gfs2/inode.c:904
__lookup_slow+0x250/0x374 fs/namei.c:1690
lookup_slow+0x60/0x84 fs/namei.c:1707
walk_component+0x280/0x36c fs/namei.c:1998
lookup_last fs/namei.c:2455 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2479
filename_lookup+0x1d4/0x4e0 fs/namei.c:2508
user_path_at_empty+0x5c/0x84 fs/namei.c:2907
user_path_at include/linux/namei.h:57 [inline]
ksys_umount fs/namespace.c:1822 [inline]
__do_sys_umount fs/namespace.c:1830 [inline]
__se_sys_umount fs/namespace.c:1828 [inline]
__arm64_sys_umount+0xf8/0x17c fs/namespace.c:1828
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015a14e70 (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: ffff800015a15670 (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: ffff800015a14ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
1 lock held by klogd/3832:
2 locks held by getty/3985:
#0: ffff0000d5c03098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bca32f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
1 lock held by syz-executor.2/4251:
#0: ffff0000f80a0150 (&type->i_mutex_dir_key#16){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000f80a0150 (&type->i_mutex_dir_key#16){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706

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



---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cdfd0a7f0139 Linux 5.15.154
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=123ee961180000
kernel config: https://syzkaller.appspot.com/x/.config?x=a0d657e4df0a8dde
dashboard link: https://syzkaller.appspot.com/bug?extid=7aebfd340e5ced0abdf8

compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/093210fbc9bd/disk-cdfd0a7f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dbab34a8852d/vmlinux-cdfd0a7f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e3e218d1a57e/Image-cdfd0a7f.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+7aebfd...@syzkaller.appspotmail.com

INFO: task syz-executor.0:3976 blocked for more than 143 seconds.
Not tainted 5.15.154-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor.0 state:D stack: 0 pid: 3976 ppid: 1 flags:0x00000005
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459

bit_wait+0x1c/0xac kernel/sched/wait_bit.c:199
__wait_on_bit kernel/sched/wait_bit.c:49 [inline]

out_of_line_wait_on_bit+0x208/0x33c kernel/sched/wait_bit.c:64
wait_on_bit include/linux/wait_bit.h:76 [inline]
gfs2_glock_wait fs/gfs2/glock.c:1280 [inline]
gfs2_glock_nq+0xb38/0x144c fs/gfs2/glock.c:1536
gfs2_glock_nq_init fs/gfs2/glock.h:246 [inline]
__gfs2_lookup+0x114/0x260 fs/gfs2/inode.c:882
gfs2_lookup+0x2c/0x3c fs/gfs2/inode.c:907
__lookup_slow+0x250/0x388 fs/namei.c:1663
lookup_slow+0x60/0x84 fs/namei.c:1680
walk_component+0x394/0x4cc fs/namei.c:1976
lookup_last fs/namei.c:2431 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2455
filename_lookup+0x1c4/0x4c8 fs/namei.c:2484
user_path_at_empty+0x5c/0x1a4 fs/namei.c:2883
user_path_at include/linux/namei.h:57 [inline]
ksys_umount fs/namespace.c:1779 [inline]
__do_sys_umount fs/namespace.c:1787 [inline]
__se_sys_umount fs/namespace.c:1785 [inline]
__arm64_sys_umount+0xf8/0x17c fs/namespace.c:1785
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:

2 locks held by kworker/u4:0/9:
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:475 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1621 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x328/0x1e48 kernel/sched/core.c:6290
#1: ffff0001b47ebc48 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x438/0x66c kernel/sched/psi.c:891
1 lock held by khungtaskd/27:
#0: ffff800014b114e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:311
1 lock held by klogd/3572:
2 locks held by getty/3718:
#0: ffff0000d3b82098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a3be2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
1 lock held by syz-executor.0/3976:
#0: ffff0000edc48818 (&type->i_mutex_dir_key#12){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000edc48818 (&type->i_mutex_dir_key#12){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: fa3df276cd36 Linux 5.15.155
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117b1547180000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa45dfd65a261480

dashboard link: https://syzkaller.appspot.com/bug?extid=7aebfd340e5ced0abdf8
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=104082dd180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11dc3593180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0dc19fc63531/disk-fa3df276.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fae4c89e243a/vmlinux-fa3df276.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a5c832fcb939/Image-fa3df276.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9ac148012f2f/mount_0.gz

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

INFO: task syz-executor411:4004 blocked for more than 143 seconds.
Not tainted 5.15.155-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor411 state:D stack: 0 pid: 4004 ppid: 4002 flags:0x00000004

1 lock held by khungtaskd/27:
#0: ffff800014b114e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:311

2 locks held by getty/3724:
#0: ffff0000d2ad2098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018e262e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
1 lock held by syz-executor411/4004:
#0: ffff0000df4e2338 (&type->i_mutex_dir_key#6){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000df4e2338 (&type->i_mutex_dir_key#6){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679

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



---
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.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: f2295faba5e8 Linux 6.1.88
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1044556b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=508163b9ab79dc25

dashboard link: https://syzkaller.appspot.com/bug?extid=90f9c53a8e1181aa3f4b
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=124580a7180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13203327180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/db6c44dd5d81/disk-f2295fab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/96a1c7aa1507/vmlinux-f2295fab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84353702f58a/Image-f2295fab.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3f2775e564eb/mount_0.gz

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

INFO: task syz-executor145:4263 blocked for more than 143 seconds.
Not tainted 6.1.88-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor145 state:D stack:0 pid:4263 ppid:4261 flags:0x00000004

#0: ffff800015a24e70 (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: ffff800015a25670 (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: ffff800015a24ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by getty/3989:
#0: ffff0000d632c098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bcd02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
1 lock held by syz-executor145/4263:
#0: ffff0000e20b3710 (&type->i_mutex_dir_key#6){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e20b3710 (&type->i_mutex_dir_key#6){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706

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



---