From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754024AbcHSFAi (ORCPT <rfc822;w@1wt.eu>);
        Fri, 19 Aug 2016 01:00:38 -0400
Received: from mail-wm0-f68.google.com ([74.125.82.68]:33565 "EHLO
        mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752314AbcHSFAg (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 19 Aug 2016 01:00:36 -0400
Date: Thu, 18 Aug 2016 18:36:56 +0200
From: Ingo Molnar <mingo@kernel.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        "H . Peter Anvin" <hpa@zytor.com>, x86@kernel.org,
        linux-kernel@vger.kernel.org, Andy Lutomirski <luto@amacapital.net>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Steven Rostedt <rostedt@goodmis.org>, Brian Gerst <brgerst@gmail.com>,
        Kees Cook <keescook@chromium.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Byungchul Park <byungchul.park@lge.com>,
        Nilay Vaish <nilayvaish@gmail.com>
Subject: Re: [PATCH v4 00/57] x86/dumpstack: rewrite x86 stack dump code
Message-ID: <20160818163656.GA3858@gmail.com>
References: <cover.1471525031.git.jpoimboe@redhat.com>
 <20160818132507.GD22490@lerouge>
 <20160818133935.GA3737@gmail.com>
 <20160818143136.wogmldvu7tysmd5q@treble>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160818143136.wogmldvu7tysmd5q@treble>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Josh Poimboeuf <jpoimboe@redhat.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