diff options
| author |   Takashi Iwai <tiwai@suse.de> | 2020-10-23 09:46:55 +0200 |
|---|---|---|
| committer |   Alex Deucher <alexander.deucher@amd.com> | 2020-10-26 17:19:15 -0400 |
| commit | 8b7dc1fe1a5c1093551f6cd7dfbb941bd9081c2e (patch) | |
| tree | 7c6217bfcf0da1ee3c6446b3f09aec10409f642e /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | drm/amd/display: Fix kernel panic by dal_gpio_open() error (diff) | |
| download | wireguard-linux-8b7dc1fe1a5c1093551f6cd7dfbb941bd9081c2e.tar.xz wireguard-linux-8b7dc1fe1a5c1093551f6cd7dfbb941bd9081c2e.zip | |
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>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions