linux-kernel - possible deadlock in console

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <ebc01f4f-5b1d-4f8a-1d0d-463d5218ee45@huawei.com>
Date:   Sat, 16 Feb 2019 14:36:48 +0800
From:   Yao HongBo <yaohongbo@...wei.com>
To:     <sergey.senozhatsky@...il.com>, <linuxarm@...wei.com>,
        <linux-kernel@...r.kernel.org>
Subject: possible deadlock in console_unlock

hi, sergey:

As shown in that link, https://lkml.org/lkml/2018/6/6/397

On the linux kernel 5.0-rc6, Syzkaller also hit 'possible deadlock in console_unlock'
bug for several times in my environment.

This solution fixes things for me. Do you have a plan to submit patches to
solve this problem.

diff --git a/drivers/tty/tty_buffer.c b/drivers/tty/tty_buffer.c
	__printk_safe_enter();
	kmalloc(sizeof(struct tty_buffer) + 2 * size, GFP_ATOMIC);
	__printk_safe_exit();



Best regards,
Hongbo