linux-kernel - Re: [PATCH 00/10] printk: Avoid deadlock in NMI + vprintk

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 2 Jun 2015 11:52:53 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	"long.wanglong" <long.wanglong@...wei.com>
cc:	Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>,
	Petr Mladek <pmladek@...e.cz>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Dave Anderson <anderson@...hat.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Kay Sievers <kay@...y.org>, Michal Hocko <mhocko@...e.cz>,
	linux-kernel@...r.kernel.org, peifeiyue@...wei.com,
	dzickus@...hat.com, morgan.wang@...wei.com, sasha.levin@...cle.com,
	xuhanbing@...wei.com
Subject: Re: [PATCH 00/10] printk: Avoid deadlock in NMI + vprintk_emit()
 cleanup

On Tue, 2 Jun 2015, long.wanglong wrote:

> How about replacing printk function earlier? we can replace printk 
> function before we calling default_do_nmi(arch/x86/kernel/nmi.c) and 
> replace back after calling.
> 
> Is it a feasible solution? or does it introduce other problems?

This has been already discussed in the past when we were fixing the 
NMI-based stackdumping. See

	http://marc.info/?l=linux-kernel&m=141640218702588&w=2

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/