linux-kernel - [PATCH 0/5] printk: Use whole ring buffer + some clean up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 14 Feb 2014 17:47:31 +0100
From:	Petr Mladek <pmladek@...e.cz>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jan Kara <jack@...e.cz>, Michal Hocko <mhocko@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>,
	Petr Mladek <pmladek@...e.cz>
Subject: [PATCH 0/5] printk: Use whole ring buffer + some clean up

I have found few small problems when working on safe printk in NMI context.
The NMI stuff still needs some love. Here is the independent stuff that is
ready to go.

1st and 5th patch do small optimizations. They remove a duplicate computation.

2nd patch removes some unused code.

3rd patch adds a comment that would have saved me some time when trying to
understand the code. Well, maybe it is useful only for kernel newbies
like me ;-)

4th patch fixes two problems from the "by-one" department. They caused that
we have newer used the last 4 bytes of the ring buffer.

Petr Mladek (5):
  printk: Remove duplicated check for log level
  printk: Remove obsolete check for log level "c"
  printk: Add comment about tricky check for text buffer size
  printk: Use also the last bytes in the ring buffer
  printk: Do not compute the size of the message twice

 include/linux/printk.h | 10 +++-------
 kernel/printk/printk.c | 13 ++++++++-----
 2 files changed, 11 insertions(+), 12 deletions(-)

-- 
1.8.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/