linux-kernel - Re: [GIT PULL] tracing/NMI/printk: Use seq_buf for safe printing from NMI context

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Dec 2014 20:20:35 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jiri Kosina <jkosina@...e.cz>, Petr Mladek <pmladek@...e.cz>
Subject: Re: [GIT PULL] tracing/NMI/printk: Use seq_buf for safe printing from
 NMI context

On Mon, Dec 8, 2014 at 7:08 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> One added bonus is that this code also makes the NMI dump stack work on
> PREEMPT_RT kernels. As printk() includes sleeping locks on PREEMPT_RT,
> printk() only writes to console if the console does not use any
> rt_mutex converted spin locks. Which a lot do.

Would it perhaps be possible/reasonable to also use this to get rid of
the horrible "early_printk()" stuff, and switch to "vprintk_default"
only once the system is sufficiently up-and-running?

Hmm? Not that there are very many users of that horrible thing.

                   Linus
--
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/