printk: fix string termination for record_print_text()
authorJohn Ogness <john.ogness@linutronix.de>
Sun, 24 Jan 2021 20:27:28 +0000 (21:33 +0106)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 30 Jan 2021 12:55:20 +0000 (13:55 +0100)
commitd5ac8304e18025a522b5d1d87629e926064ce134
tree7cc4bbafa07455753254de90b55c67893427ea15
parent861c2e349a36868f9c19a82844b2eb0abf20939b
printk: fix string termination for record_print_text()

commit 08d60e5999540110576e7c1346d486220751b7f9 upstream.

Commit f0e386ee0c0b ("printk: fix buffer overflow potential for
print_text()") added string termination in record_print_text().
However it used the wrong base pointer for adding the terminator.
This led to a 0-byte being written somewhere beyond the buffer.

Use the correct base pointer when adding the terminator.

Fixes: f0e386ee0c0b ("printk: fix buffer overflow potential for print_text()")
Reported-by: Sven Schnelle <svens@linux.ibm.com>
Signed-off-by: John Ogness <john.ogness@linutronix.de>
Signed-off-by: Petr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20210124202728.4718-1-john.ogness@linutronix.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
kernel/printk/printk.c