sysrq,kdb: Use __handle_sysrq() for kdb's sysrq function

The kdb code should not toggle the sysrq state in case an end user
wants to try and resume the normal kernel execution.

Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

+3 -3
+1 -1
drivers/char/sysrq.c
··· 493 493 sysrq_key_table[i] = op_p; 494 494 } 495 495 496 - static void __handle_sysrq(int key, struct tty_struct *tty, int check_mask) 496 + void __handle_sysrq(int key, struct tty_struct *tty, int check_mask) 497 497 { 498 498 struct sysrq_key_op *op_p; 499 499 int orig_log_level;
+1
include/linux/sysrq.h
··· 45 45 */ 46 46 47 47 void handle_sysrq(int key, struct tty_struct *tty); 48 + void __handle_sysrq(int key, struct tty_struct *tty, int check_mask); 48 49 int register_sysrq_key(int key, struct sysrq_key_op *op); 49 50 int unregister_sysrq_key(int key, struct sysrq_key_op *op); 50 51 struct sysrq_key_op *__sysrq_get_key_op(int key);
+1 -2
kernel/debug/kdb/kdb_main.c
··· 1820 1820 { 1821 1821 if (argc != 1) 1822 1822 return KDB_ARGCOUNT; 1823 - sysrq_toggle_support(1); 1824 1823 kdb_trap_printk++; 1825 - handle_sysrq(*argv[1], NULL); 1824 + __handle_sysrq(*argv[1], NULL, 0); 1826 1825 kdb_trap_printk--; 1827 1826 1828 1827 return 0;