[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160818163656.GA3858@gmail.com>
Date: Thu, 18 Aug 2016 18:36:56 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-kernel@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Brian Gerst <brgerst@...il.com>,
Kees Cook <keescook@...omium.org>,
Peter Zijlstra <peterz@...radead.org>,
Byungchul Park <byungchul.park@....com>,
Nilay Vaish <nilayvaish@...il.com>
Subject: Re: [PATCH v4 00/57] x86/dumpstack: rewrite x86 stack dump code
* Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> You're right, that would be better. My apologies for spamming. It
> started with "only" 19 patches in v1 and then quickly got out of hand.
np!
> I may split it up something like this:
>
> cleanups:
> function graph fixes:
> get_stack_info():
> unwinder prep:
> unwinder:
> hardened usercopy:
> standardize the end of the stack:
> pt_regs frames:
> unwinder warnings:
Looks good to me, but please always keep only one of these series 'in flight' -
i.e. wait until it's been reviewed & applied before proceeding to the next series.
That helps us keep all sane and relaxed!
Thanks,
Ingo
Powered by blists - more mailing lists