linux-kernel - Re: [RFC][PATCH 0/5 v2] x86/nmi: Print all cpu stacks from NMI safely

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:	Fri, 8 Aug 2014 14:44:12 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Michal Hocko <mhocko@...e.cz>, Jan Kara <jack@...e.cz>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Dave Anderson <anderson@...hat.com>,
	Petr Mladek <pmladek@...e.cz>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Konstantin Khlebnikov <koct9i@...il.com>
Subject: Re: [RFC][PATCH 0/5 v2] x86/nmi: Print all cpu stacks from NMI
 safely

On Thu, 7 Aug 2014 10:41:45 +0200 (CEST)
Jiri Kosina <jkosina@...e.cz> wrote:

> On Thu, 26 Jun 2014, Steven Rostedt wrote:
> 
> > This is version 2:
> > 
> > This is my proposal to print the NMI stack traces from an RCU stall safely.
> > Here's the gist of it.
> 
> Steven, what's your plan with this patchset please? 

Has there been consensus on this approach?

> 
> It has been tested by Petr here on the systems under the loads that are 
> able to trigger the hangs.
> 
> It'd be nice to have this in 3.17, so that we can then start working on 
> fixing all the remaining printk() calls in NMI context once this biggest 
> offender (stack dumping) is done.

It definitely wont be in 3.17 (too late). I'm fine with getting this
ready unless there's other objections.

3.17 does contain the updates to trace_seq that Andrew made. Linus had
issues with the "trace" name, which this patch set creates a new
"seq_buf" that is a subset of the trace_seq.

I'll keep this on my todo list for 3.18 and push out patches to get
people's comments about it after 3.17 merge window has closed (the
required people are a bit busy at the moment).

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