[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180221112631.GA19900@kroah.com>
Date: Wed, 21 Feb 2018 12:26:31 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: stable@...r.kernel.org, Josh Poimboeuf <jpoimboe@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Andrew Morton <akpm@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [stable 4.14 patch] x86: fix KMEMCHECK warning about
FRAME_POINTER
On Fri, Feb 16, 2018 at 04:29:10PM +0100, Arnd Bergmann wrote:
> When KMEMCHECK is enabled without UNWINDER_FRAME_POINTER, we get a
> Kconfig warning, presumably harmless:
>
> warning: (FAULT_INJECTION_STACKTRACE_FILTER && LATENCYTOP && KMEMCHECK && LOCKDEP && UNWINDER_FRAME_POINTER) selects FRAME_POINTER which has unmet direct dependencies (DEBUG_KERNEL && (CRIS || M68K || FRV || UML || SUPERH || BLACKFIN || MN10300 || METAG) || ARCH_WANT_FRAME_POINTERS || !UNWINDER_ORC && !UNWINDER_GUESS)
>
> In newer mainline kernels, the KMEMCHECK option has been removed, so
> this no longer happens. Adding the unwinder as a direct dependency
> for KMEMCHECK works for 4.14-stable as well and documents the
> dependency better.
4.14.y now has that option removed as well, as I just removed all of
kmemcheck as it was "getting in the way" of other patches, so this isn't
needed anymore.
thanks,
greg k-h
Powered by blists - more mailing lists