From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 29 Apr 2016 21:45:58 +0800 From: Minfei Huang Subject: Re: [RFC PATCH v2 06/18] x86: dump_trace() error handling Message-ID: <20160429134558.GA17476@dhcp-128-44.nay.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Archive: To: Josh Poimboeuf Cc: Jessica Yu , Jiri Kosina , Miroslav Benes , Ingo Molnar , Peter Zijlstra , Michael Ellerman , Heiko Carstens , live-patching@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, Vojtech Pavlik , Jiri Slaby , Petr Mladek , Chris J Arges , Andy Lutomirski List-ID: On 04/28/16 at 03:44P, Josh Poimboeuf wrote: > In preparation for being able to determine whether a given stack trace > is reliable, allow the stacktrace_ops functions to propagate errors to > dump_trace(). Hi, Josh. Have you considered to make walk_stack function as non-return function, since there is no obvious error during detecting the frame points? Thanks Minfei