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

Date:	Thu, 11 Dec 2014 11:41:21 -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 Thu, Dec 11, 2014 at 3:33 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> So you are saying that anytime the printk_func is not the default, the
> caller had to have disable preemption?

Yes. That, or change all of the vprintk_func entries. Otherwise, the
caller itself obviously doesn't know which cpu version it would get,
so disabling preemption inside printk is simply much too late.

                     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/