drm/amd/display: Don't invoke kgdb_breakpoint() unconditionally

ASSERT_CRITICAL() invokes kgdb_breakpoint() whenever either
CONFIG_KGDB or CONFIG_HAVE_KGDB is set.  This, however, may lead to a
kernel panic when no kdb stuff is attached, since the
kgdb_breakpoint() call issues INT3.  It's nothing but a surprise for
normal end-users.

For avoiding the pitfall, make the kgdb_breakpoint() call only when
CONFIG_DEBUG_KERNEL_DC is set.

https://bugzilla.opensuse.org/show_bug.cgi?id=1177973
Cc: <stable@vger.kernel.org>
Acked-by: Alex Deucher <alexander.deucher@amd.com>
Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
This commit is contained in:
Takashi Iwai 2020-10-23 09:46:55 +02:00 committed by Alex Deucher
parent 594b6f7370
commit 0ca3418272
1 changed files with 1 additions and 1 deletions

View File

@ -94,7 +94,7 @@
* general debug capabilities * general debug capabilities
* *
*/ */
#if defined(CONFIG_HAVE_KGDB) || defined(CONFIG_KGDB) #if defined(CONFIG_DEBUG_KERNEL_DC) && (defined(CONFIG_HAVE_KGDB) || defined(CONFIG_KGDB))
#define ASSERT_CRITICAL(expr) do { \ #define ASSERT_CRITICAL(expr) do { \
if (WARN_ON(!(expr))) { \ if (WARN_ON(!(expr))) { \
kgdb_breakpoint(); \ kgdb_breakpoint(); \