[v5.15] BUG: sleeping function called from invalid context in console_lock (2)

Hello,

syzbot found the following issue on:

HEAD commit: b95c01af2113 Linux 5.15.152
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11db4fb6180000
kernel config: https://syzkaller.appspot.com/x/.config?x=b26cb65e5b8ad5c7
dashboard link: https://syzkaller.appspot.com/bug?extid=37e68cdad38ff6f2bde3
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5cd4262a21bb/disk-b95c01af.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/85698e4f8310/vmlinux-b95c01af.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f57a616768d4/bzImage-b95c01af.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

BUG: sleeping function called from invalid context at kernel/printk/printk.c:2549
in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 21546, name: syz-executor.1
3 locks held by syz-executor.1/21546:
#0: ffff88806a757098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffff88806a757130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:961 [inline]
#1: ffff88806a757130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:984 [inline]
#1: ffff88806a757130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write+0x24f/0x920 drivers/tty/tty_io.c:1110
#2: ffff88807dc6f398 (&gsm->tx_lock){....}-{2:2}, at: gsmld_write+0x5b/0x120 drivers/tty/n_gsm.c:2926
irq event stamp: 68
hardirqs last enabled at (67): [<ffffffff8a1bd41e>] syscall_enter_from_user_mode+0x2e/0x230 kernel/entry/common.c:107
hardirqs last disabled at (68): [<ffffffff8a25433c>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]
hardirqs last disabled at (68): [<ffffffff8a25433c>] _raw_spin_lock_irqsave+0xac/0x120 kernel/locking/spinlock.c:162
softirqs last enabled at (0): [<ffffffff814b2ee9>] copy_process+0x13b9/0x3ef0 kernel/fork.c:2151
softirqs last disabled at (0): [<0000000000000000>] 0x0
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 1 PID: 21546 Comm: syz-executor.1 Not tainted 5.15.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
___might_sleep+0x547/0x6a0 kernel/sched/core.c:9626
console_lock+0x18/0x70 kernel/printk/printk.c:2549
do_con_write+0x110/0x7270 drivers/tty/vt/vt.c:2908
con_write+0x20/0x40 drivers/tty/vt/vt.c:3295
gsmld_write+0xf9/0x120 drivers/tty/n_gsm.c:2929
do_tty_write drivers/tty/tty_io.c:1038 [inline]
file_tty_write+0x561/0x920 drivers/tty/tty_io.c:1110
call_write_iter include/linux/fs.h:2148 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fac1dfb7da9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fac1c5170c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fac1e0e6050 RCX: 00007fac1dfb7da9
RDX: 00000000000008ad RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 00007fac1e00447a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fac1e0e6050 R15: 00007ffe92700d68
</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 [email protected].

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 has found a reproducer for the following issue on:

HEAD commit: 4878aadf2d15 Linux 5.15.161
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12242746980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c85789a8132e5ce2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15233f0e980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1498539c980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cc5f5c64b111/disk-4878aadf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/13d63675f578/vmlinux-4878aadf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/11bcc3354434/Image-4878aadf.gz.xz
BUG: sleeping function called from invalid context at kernel/printk/printk.c:2555
in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 4024, name: syz-executor187
3 locks held by syz-executor187/4024:
#0: ffff0000cd343098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff0000cd343130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:961 [inline]
#1: ffff0000cd343130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:984 [inline]
#1: ffff0000cd343130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write+0x1d4/0x758 drivers/tty/tty_io.c:1110
#2: ffff0000cd342398 (&gsm->tx_lock){....}-{2:2}, at: gsmld_write+0x60/0x164 drivers/tty/n_gsm.c:2983
irq event stamp: 9286
hardirqs last enabled at (9285): [<ffff800011a72328>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
hardirqs last enabled at (9285): [<ffff800011a72328>] _raw_spin_unlock_irqrestore+0xac/0x158 kernel/locking/spinlock.c:194
hardirqs last disabled at (9286): [<ffff800011a71e04>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]
hardirqs last disabled at (9286): [<ffff800011a71e04>] _raw_spin_lock_irqsave+0xfc/0x14c kernel/locking/spinlock.c:162
softirqs last enabled at (9266): [<ffff8000080308b0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (9264): [<ffff80000803087c>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
Preemption disabled at:
[<ffff80000b4108d8>] gsmld_write+0x60/0x164 drivers/tty/n_gsm.c:2983
CPU: 0 PID: 4024 Comm: syz-executor187 Not tainted 5.15.161-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
___might_sleep+0x380/0x4dc kernel/sched/core.c:9626
__might_sleep+0x98/0xf0 kernel/sched/core.c:9580
console_lock+0x30/0x16c kernel/printk/printk.c:2555
do_con_write+0x110/0x5934 drivers/tty/vt/vt.c:2908
con_write+0x34/0x58 drivers/tty/vt/vt.c:3295
gsmld_write+0x108/0x164 drivers/tty/n_gsm.c:2986
do_tty_write drivers/tty/tty_io.c:1038 [inline]
file_tty_write+0x44c/0x758 drivers/tty/tty_io.c:1110
tty_write+0x48/0x58 drivers/tty/tty_io.c:1131
call_write_iter include/linux/fs.h:2172 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x87c/0xb3c fs/read_write.c:594
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__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


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