Christophe Leroy dded2e1592 kdb: use correct pointer when 'btc' calls 'btt' ... On a powerpc 8xx, 'btc' fails as follows: Entering kdb (current=0x(ptrval), pid 282) due to Keyboard Entry kdb> btc btc: cpu status: Currently on cpu 0 Available cpus: 0 kdb_getarea: Bad address 0x0 when booting the kernel with 'debug_boot_weak_hash', it fails as well Entering kdb (current=0xba99ad80, pid 284) due to Keyboard Entry kdb> btc btc: cpu status: Currently on cpu 0 Available cpus: 0 kdb_getarea: Bad address 0xba99ad80 On other platforms, Oopses have been observed too, see https://github.com/linuxppc/linux/issues/139 This is due to btc calling 'btt' with %p pointer as an argument. This patch replaces %p by %px to get the real pointer value as expected by 'btt' Fixes: ad67b74d24 ("printk: hash addresses printed with %p") Cc: <stable@vger.kernel.org> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr> Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>		2018-11-13 20:27:16 +00:00
..
.gitignore
kdb_bp.c	kdb: bl: don't use tab character in output	2018-01-25 08:41:22 -06:00
kdb_bt.c	kdb: use correct pointer when 'btc' calls 'btt'	2018-11-13 20:27:16 +00:00
kdb_cmds	kdb: cleanup unused variables missed in the original kdb merge	2011-08-01 13:23:58 -05:00
kdb_debugger.c	kgdb: timeout if secondary CPUs ignore the roundup	2014-11-11 09:31:53 -06:00
kdb_io.c	kdb: Fix handling of kallsyms_symbol_next() return value	2017-12-06 16:12:43 -06:00
kdb_keyboard.c	KDB: Fix usability issues relating to the 'enter' key.	2012-03-22 15:07:15 -05:00
kdb_main.c	sched: loadavg: consolidate LOAD_INT, LOAD_FRAC, CALC_LOAD	2018-10-26 16:26:32 -07:00
kdb_private.h	signal: Simplify and fix kdb_send_sig	2018-01-03 18:01:08 -06:00
kdb_support.c	kdb: use memmove instead of overlapping memcpy	2018-02-04 21:29:53 -06:00
Makefile