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 S1754709AbbETR1Y (ORCPT <rfc822;w@1wt.eu>);
	Wed, 20 May 2015 13:27:24 -0400
Received: from casper.infradead.org ([85.118.1.10]:35330 "EHLO
	casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751609AbbETR1V (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 20 May 2015 13:27:21 -0400
Date: Wed, 20 May 2015 19:27:00 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Ingo Molnar <mingo@kernel.org>, Josh Poimboeuf <jpoimboe@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>, Michal Marek <mmarek@suse.cz>,
        X86 ML <x86@kernel.org>, live-patching@vger.kernel.org,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Andy Lutomirski <luto@kernel.org>,
        Denys Vlasenko <dvlasenk@redhat.com>, Brian Gerst <brgerst@gmail.com>,
        Borislav Petkov <bp@alien8.de>,
        Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v4 0/3] Compile-time stack frame pointer validation
Message-ID: <20150520172700.GM3644@twins.programming.kicks-ass.net>
References: <cover.1431966710.git.jpoimboe@redhat.com>
 <20150520103339.GA22205@gmail.com>
 <20150520141331.GA16995@treble.redhat.com>
 <20150520144810.GA10374@gmail.com>
 <CALCETrWAP=7dN8P3dn0JwYTn2SHYtyi-3z7KqGcjV0X6d=s50g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALCETrWAP=7dN8P3dn0JwYTn2SHYtyi-3z7KqGcjV0X6d=s50g@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2012-12-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, May 20, 2015 at 09:03:37AM -0700, Andy Lutomirski wrote:
> I think it would be nice to have full DWARF unwind support for
> everything at some point.  Unfortunately, I don't see any easy path to
> getting there.  It doesn't help that AFAIK no one has ever proposed a
> usable in-kernel DWARF unwinder.

There's a bit of history here; SuSE (iirc) actually has one, however:

  https://lkml.org/lkml/2012/2/10/356