[v5.15] INFO: task hung in gfs2_jhead_process_page

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13845a5cc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b57cfa804330c3b7
dashboard link: https://syzkaller.appspot.com/bug?extid=6ad5b9584d4f1a15790b
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8088989394e3/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2651d6753959/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3fa3f994f9a/Image-d9b4a0c8.gz.xz

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

INFO: task kworker/1:17:6920 blocked for more than 143 seconds.
Not tainted 5.15.98-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:17 state:D stack: 0 pid: 6920 ppid: 2 flags:0x00000008
Workqueue: gfs_recovery gfs2_recover_func
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0xfb4/0x1eec kernel/sched/core.c:6369
schedule+0x11c/0x1c8 kernel/sched/core.c:6452
io_schedule+0x8c/0x194 kernel/sched/core.c:8469
wait_on_page_bit_common+0x6fc/0xc14 mm/filemap.c:1356
wait_on_page_bit+0x58/0x68 mm/filemap.c:1417
wait_on_page_locked include/linux/pagemap.h:688 [inline]
gfs2_jhead_process_page+0x1e0/0x6b0 fs/gfs2/lops.c:476
gfs2_find_jhead+0x814/0xdb4 fs/gfs2/lops.c:586
gfs2_recover_func+0x548/0x17fc fs/gfs2/recovery.c:462
process_one_work+0x82c/0x1478 kernel/workqueue.c:2306
worker_thread+0x910/0x1034 kernel/workqueue.c:2453
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 <unknown>:870
INFO: task syz-executor.2:9047 blocked for more than 143 seconds.
Not tainted 5.15.98-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack: 0 pid: 9047 ppid: 4079 flags:0x00000009
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0xfb4/0x1eec kernel/sched/core.c:6369
schedule+0x11c/0x1c8 kernel/sched/core.c:6452
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_recover_journal+0xf0/0x16c fs/gfs2/recovery.c:579
init_journal+0x1550/0x20f4 fs/gfs2/ops_fstype.c:837
init_inodes+0xe0/0x2d8 fs/gfs2/ops_fstype.c:891
gfs2_fill_super+0x1640/0x2010 fs/gfs2/ops_fstype.c:1249
get_tree_bdev+0x360/0x54c fs/super.c:1294
gfs2_get_tree+0x54/0x1b4 fs/gfs2/ops_fstype.c:1332
vfs_get_tree+0x90/0x274 fs/super.c:1499
do_new_mount+0x25c/0x8c8 fs/namespace.c:2994
path_mount+0x590/0x104c fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 <unknown>:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014b026a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:266
2 locks held by getty/3736:
#0: ffff0000d3c58098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a2db2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
2 locks held by kworker/1:5/4130:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x1478 kernel/workqueue.c:2279
#1: ffff80001ca17c00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x1478 kernel/workqueue.c:2281
2 locks held by kworker/1:17/6920:
#0: ffff0000c6902538 ((wq_completion)gfs_recovery){+.+.}-{0:0}, at: process_one_work+0x66c/0x1478 kernel/workqueue.c:2279
#1: ffff80001dd27c00 ((work_completion)(&jd->jd_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x1478 kernel/workqueue.c:2281
1 lock held by syz-executor.2/9047:
#0: ffff0000c175a0e0 (&type->s_umount_key#46/1){+.+.}-{3:3}, at: alloc_super+0x1b8/0x844 fs/super.c:229
1 lock held by udevd/9090:
2 locks held by syz-executor.2/12448:
3 locks held by syz-executor.0/12446:
2 locks held by syz-executor.0/12453:
2 locks held by syz-executor.3/12445:

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



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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10768f26c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=29ad3fe3c7b61175
dashboard link: https://syzkaller.appspot.com/bug?extid=b18d60b52daf3883ffe4

compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/34f95428f5fb/disk-7eaef76f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1bdd9b2c390d/vmlinux-7eaef76f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/419140981cfa/Image-7eaef76f.gz.xz

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

Reported-by: syzbot+b18d60...@syzkaller.appspotmail.com

INFO: task kworker/0:0:7 blocked for more than 143 seconds.
Not tainted 6.1.20-syzkaller #0

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

task:kworker/0:0 state:D stack:0 pid:7 ppid:2 flags:0x00000008

Workqueue: gfs_recovery gfs2_recover_func
Call trace:

__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5238 [inline]
__schedule+0xf9c/0x1d84 kernel/sched/core.c:6551
schedule+0xc4/0x170 kernel/sched/core.c:6627
io_schedule+0x8c/0x188 kernel/sched/core.c:8771
folio_wait_bit_common+0x65c/0xb90 mm/filemap.c:1296
folio_wait_bit+0x30/0x40 mm/filemap.c:1440
folio_wait_locked include/linux/pagemap.h:1022 [inline]
gfs2_jhead_process_page+0x150/0x5c0 fs/gfs2/lops.c:476
gfs2_find_jhead+0xa58/0xbe0 fs/gfs2/lops.c:594
gfs2_recover_func+0x550/0x18f0 fs/gfs2/recovery.c:460
process_one_work+0x868/0x16f4 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
INFO: task syz-executor.2:5182 blocked for more than 143 seconds.
Not tainted 6.1.20-syzkaller #0

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

task:syz-executor.2 state:D stack:0 pid:5182 ppid:4337 flags:0x00000009
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5238 [inline]
__schedule+0xf9c/0x1d84 kernel/sched/core.c:6551
schedule+0xc4/0x170 kernel/sched/core.c:6627

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_recover_journal+0xd8/0x150 fs/gfs2/recovery.c:577
init_journal+0x15c0/0x2200 fs/gfs2/ops_fstype.c:835
init_inodes+0xe0/0x2d8 fs/gfs2/ops_fstype.c:889
gfs2_fill_super+0x1608/0x1f9c fs/gfs2/ops_fstype.c:1247
get_tree_bdev+0x360/0x54c fs/super.c:1337
gfs2_get_tree+0x54/0x1b4 fs/gfs2/ops_fstype.c:1330
vfs_get_tree+0x90/0x274 fs/super.c:1544
do_new_mount+0x25c/0x8c8 fs/namespace.c:3040
path_mount+0x590/0xe58 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
__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:581

Showing all locks held in the system:

2 locks held by kworker/0:0/7:
#0: ffff0000c5428938 ((wq_completion)gfs_recovery){+.+.}-{0:0}, at: process_one_work+0x664/0x16f4 kernel/workqueue.c:2262
#1: ffff800019ce7c20 ((work_completion)(&jd->jd_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x16f4 kernel/workqueue.c:2264
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015905db0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffff8000159065b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffff800015905be0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
1 lock held by syslogd/3823:
#0: ffff0001b4591598 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:537 [inline]
#0: ffff0001b4591598 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1354 [inline]
#0: ffff0001b4591598 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1644 [inline]
#0: ffff0001b4591598 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x2c8/0x1d84 kernel/sched/core.c:6468
2 locks held by getty/3997:
#0: ffff0000d3e5b098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bbb02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
1 lock held by syz-executor.2/5182:
#0: ffff00011df2e0e0 (&type->s_umount_key#60/1){+.+.}-{3:3}, at: alloc_super+0x1b4/0x824 fs/super.c:228
2 locks held by syz-executor.5/7748:
3 locks held by syz-executor.4/7750:

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 2f3918bc53fb Linux 6.1.33
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1209c5e7280000
kernel config: https://syzkaller.appspot.com/x/.config?x=64e29382e385f1b9

dashboard link: https://syzkaller.appspot.com/bug?extid=b18d60b52daf3883ffe4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11eff265280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14887563280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f180a77b248f/disk-2f3918bc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/582d3206652e/vmlinux-2f3918bc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/20934119e0f6/Image-2f3918bc.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3cc96b535995/mount_0.gz

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

INFO: task syz-executor422:4240 blocked for more than 143 seconds.
Not tainted 6.1.33-syzkaller #0

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

task:syz-executor422 state:D stack:0 pid:4240 ppid:4239 flags:0x00000009

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
io_schedule+0x8c/0x188 kernel/sched/core.c:8774

folio_wait_bit_common+0x65c/0xb90 mm/filemap.c:1296
folio_wait_bit+0x30/0x40 mm/filemap.c:1440
folio_wait_locked include/linux/pagemap.h:1022 [inline]
gfs2_jhead_process_page+0x150/0x5c0 fs/gfs2/lops.c:476

gfs2_find_jhead+0x70c/0xbe0 fs/gfs2/lops.c:583
check_journal_clean+0x1a4/0x318 fs/gfs2/util.c:75
init_journal+0x14e0/0x2054 fs/gfs2/ops_fstype.c:830

init_inodes+0xe0/0x2d8 fs/gfs2/ops_fstype.c:889
gfs2_fill_super+0x1608/0x1f9c fs/gfs2/ops_fstype.c:1247

get_tree_bdev+0x360/0x54c fs/super.c:1346
gfs2_get_tree+0x54/0x1b4 fs/gfs2/ops_fstype.c:1330
vfs_get_tree+0x90/0x274 fs/super.c:1553
do_new_mount+0x25c/0x8c4 fs/namespace.c:3040

path_mount+0x590/0xe58 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
__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:581

Showing all locks held in the system:

1 lock held by rcu_tasks_kthre/12:

#0: ffff800015794df0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510

1 lock held by rcu_tasks_trace/13:

#0: ffff8000157955f0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510

1 lock held by khungtaskd/28:

#0: ffff800015794c20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3977:
#0: ffff0000d61f9098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001ba402f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
1 lock held by syz-executor422/4240:
#0: ffff0000d84760e0 (&type->s_umount_key#39/1){+.+.}-{3:3}, at: alloc_super+0x1b4/0x824 fs/super.c:228

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



---
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: 7349e40704a0 Linux 5.15.116
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1303469d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=f650a0601dbf525d

dashboard link: https://syzkaller.appspot.com/bug?extid=6ad5b9584d4f1a15790b
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136dda27280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bb01dd280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eec1263e4f05/disk-7349e407.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/833d6ae016fd/vmlinux-7349e407.xz
kernel image: https://storage.googleapis.com/syzbot-assets/da142afba386/Image-7349e407.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0f5d788ad53d/mount_0.gz

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

INFO: task syz-executor199:3985 blocked for more than 143 seconds.
Not tainted 5.15.116-syzkaller #0

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

task:syz-executor199 state:D stack: 0 pid: 3985 ppid: 3984 flags:0x00000009

Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518

context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
io_schedule+0x8c/0x194 kernel/sched/core.c:8472

wait_on_page_bit_common+0x6fc/0xc14 mm/filemap.c:1356
wait_on_page_bit+0x58/0x68 mm/filemap.c:1417
wait_on_page_locked include/linux/pagemap.h:688 [inline]
gfs2_jhead_process_page+0x1e0/0x6b0 fs/gfs2/lops.c:476
gfs2_find_jhead+0x814/0xdb4 fs/gfs2/lops.c:586

check_journal_clean+0x178/0x2ec fs/gfs2/util.c:75
init_journal+0x145c/0x1f6c fs/gfs2/ops_fstype.c:832

init_inodes+0xe0/0x2d8 fs/gfs2/ops_fstype.c:891
gfs2_fill_super+0x1640/0x2010 fs/gfs2/ops_fstype.c:1249

get_tree_bdev+0x360/0x54c fs/super.c:1303
gfs2_get_tree+0x54/0x1b4 fs/gfs2/ops_fstype.c:1332
vfs_get_tree+0x90/0x274 fs/super.c:1508
do_new_mount+0x25c/0x8c4 fs/namespace.c:2994

path_mount+0x590/0x104c fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614

el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:

#0: ffff800014ac19a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3720:
#0: ffff0000d267d098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a2ab2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
1 lock held by syz-executor199/3985:
#0: ffff0000ca9420e0 (&type->s_umount_key#40/1){+.+.}-{3:3}, at: alloc_super+0x1b8/0x844 fs/super.c:229