[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190617111626.vkqayqf3tvleff37@pathway.suse.cz>
Date: Mon, 17 Jun 2019 13:16:26 +0200
From: Petr Mladek <pmladek@...e.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Miroslav Benes <mbenes@...e.cz>, jpoimboe@...hat.com,
jikos@...nel.org, joe.lawrence@...hat.com,
kamalesh@...ux.vnet.ibm.com, live-patching@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/3] stacktrace: Remove weak version of
save_stack_trace_tsk_reliable()
Hi Thomas,
On Sun 2019-06-16 10:44:59, Thomas Gleixner wrote:
> On Tue, 11 Jun 2019, Miroslav Benes wrote:
>
> > Recent rework of stack trace infrastructure introduced a new set of
> > helpers for common stack trace operations (commit e9b98e162aa5
> > ("stacktrace: Provide helpers for common stack trace operations") and
> > related). As a result, save_stack_trace_tsk_reliable() is not directly
> > called anywhere. Livepatch, currently the only user of the reliable
> > stack trace feature, now calls stack_trace_save_tsk_reliable().
> >
> > When CONFIG_HAVE_RELIABLE_STACKTRACE is set and depending on
> > CONFIG_ARCH_STACKWALK, stack_trace_save_tsk_reliable() calls either
> > arch_stack_walk_reliable() or mentioned save_stack_trace_tsk_reliable().
> > x86_64 defines the former, ppc64le the latter. All other architectures
> > do not have HAVE_RELIABLE_STACKTRACE and include/linux/stacktrace.h
> > defines -ENOSYS returning version for them.
> >
> > In short, stack_trace_save_tsk_reliable() returning -ENOSYS defined in
> > include/linux/stacktrace.h serves the same purpose as the old weak
> > version of save_stack_trace_tsk_reliable() which is therefore no longer
> > needed.
> >
> > Cc: Thomas Gleixner <tglx@...utronix.de>
> > Signed-off-by: Miroslav Benes <mbenes@...e.cz>
>
> Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
Would you like to push this patch via your tree?
Or is it OK to push it via the livepatch tree for 5.3?
Best Regards,
Petr
Powered by blists - more mailing lists