public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk regression fixes for 5.11-rc5
Date: Thu, 21 Jan 2021 17:04:01 +0100	[thread overview]
Message-ID: <YAml8WLMo3mVSoKR@alley> (raw)

Linus,

please pull three printk fixes from

  git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-5.11-printk-rework-fixup

===============================

- Fix line counting and buffer size calculation. Both regressions
  caused that a reader buffer might not get filled as much as possible.

- Restore non-documented behavior of printk() reader API and make it
  official. It did not fill the last byte of the provided buffer before
  5.10. Two architectures, powerpc and um, used it to add
  the trailing '\0'. There might theoretically be more callers
  depending on this behavior in userspace.

===============================

All three regressions were found and fixed by John when
working on another changes.

----------------------------------------------------------------
John Ogness (3):
      printk: ringbuffer: fix line counting
      printk: fix kmsg_dump_get_buffer length calulations
      printk: fix buffer overflow potential for print_text()

Petr Mladek (1):
      Merge branch 'printk-rework' into for-linus

 kernel/printk/printk.c            | 40 ++++++++++++++++++++++++++++-----------
 kernel/printk/printk_ringbuffer.c |  2 +-
 2 files changed, 30 insertions(+), 12 deletions(-)

             reply	other threads:[~2021-01-21 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 16:04 Petr Mladek [this message]
2021-01-21 19:48 ` [GIT PULL] printk regression fixes for 5.11-rc5 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YAml8WLMo3mVSoKR@alley \
    --to=pmladek@suse.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox