tracing: do not leak kernel addresses

This likely breaks tracing tools like trace-cmd.  It logs in the same
format but now addresses are all 0x0.

Mot-CRs-fixed:(CR)
CVE-Fixed:CVE-2017-0630
Bug: 34277115

Change-Id: Ie837ab27d8f4cc164828ad70a916f3de688056cf
Reviewed-on: https://gerrit.mot.com/1875873
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Reviewed-by: Srikanth A R <arsrikan@motorola.com>
Reviewed-by: Ravikumar Vembu <Raviv@motorola.com>
Reviewed-by: Yinjun Chen <a7301c@motorola.com>
Tested-by: Yinjun Chen <a7301c@motorola.com>
Submit-Approved: Yinjun Chen <a7301c@motorola.com>

diff --git a/kernel/trace/trace_printk.c b/kernel/trace/trace_printk.c
index ad1d6164e94603cf29f1b26f0a58f8c37988d57b..e82cff5c842c6e5c8ac961cd6beae0ab0a3ab304 100644 (file)
--- a/kernel/trace/trace_printk.c
+++ b/kernel/trace/trace_printk.c
@@ -304,7 +304,7 @@ static int t_show(struct seq_file *m, void *v)
        if (!*fmt)
                return 0;
 
-       seq_printf(m, "0x%lx : \"", *(unsigned long *)fmt);
+       seq_printf(m, "0x%lx : \"", 0L);
 
        /*
         * Tabs and new lines need to be converted.