tag a24fd34fcf99907c0ce3fa762b73e5ee9b4c046b
tagger Todd Kjos <tkjos@google.com> Tue Apr 03 11:13:40 2018 -0700
object 13b40d327b49759119e86f3e9724e27d3aa3b538

https://source.android.com/security/bulletin/2018-04-01
CVE-2017-16534
CVE-2017-13293
CVE-2017-5754
CVE-2017-13305
CVE-2017-17449
CVE-2017-13307
CVE-2017-17712
CVE-2017-15115

commit 13b40d327b49759119e86f3e9724e27d3aa3b538
author Ji Zhang <ji.zhang@mediatek.com> Fri Jan 26 15:04:26 2018 +0800
committer Greg Kroah-Hartman <gregkh@google.com> Tue Apr 03 08:56:40 2018 +0000
tree 709436d1b5049fc0e560be7853a3a093e7679e26
parent 40a18300721d1bf4fb2e6fcfe0fd6784ff209b1c

arm64: fix show_data fallout from KERN_CONT changes

The log format printed by show_data is illegible due to printk change
"commit 4bcc595ccd80decb ("printk: reinstate KERN_CONT for printing
continuation lines")".

The output is like:
[   32.669636] SP: 0xffffffc0b01f7c50:
[   32.669647] 7c50
[   32.669652]  b01f7eb0
[   32.669655]  ffffffc0
[   32.669659]  00000000
[   32.669662]  00000000
[   32.669665]  00000015
[   32.669669]  00000000
[   32.669672]  00000123
[   32.669675]  00000000
[   32.669674]
[   32.669680] 7c70
[   32.669684]  0000003f
[   32.669687]  00000000
[   32.669690]  08c82000
[   32.669694]  ffffff80
[   32.669697]  b01f4000
[   32.669700]  ffffffc0
[   32.669703]  b01f7cd0
[   32.669706]  ffffffc0

To fix this, use pr_cont() instead of the printk() to print
continuing lines.

Signed-off-by: Ji Zhang <ji.zhang@mediatek.com>
Signed-off-by: Miles Chen <miles.chen@mediatek.com>