linux-kernel - [PATCH v2 0/4] printf stuff

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1443627051-14003-1-git-send-email-linux@rasmusvillemoes.dk>
Date:	Wed, 30 Sep 2015 17:30:47 +0200
From:	Rasmus Villemoes <linux@...musvillemoes.dk>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Tejun Heo <tj@...nel.org>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>,
	Joe Perches <joe@...ches.com>,
	Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: [PATCH v2 0/4] printf stuff

A few printf-related patches I've been sitting on. I also have some
documentation updates, but I'll wait until I see Martin's patch [1] in
-next. There's also the %pb issue [2], but I'm not sure there's consensus
on the best fix for that.

[1] https://lkml.org/lkml/2015/9/24/256
[2] https://lkml.org/lkml/2015/9/16/769

Rasmus Villemoes (4):
  lib/vsprintf.c: handle invalid format specifiers more robustly
  lib/vsprintf.c: also improve sanity check in bstr_printf()
  lib/vsprintf.c: Remove SPECIAL handling in pointer()
  test_printf: test printf family at runtime

 lib/Kconfig.debug |   3 +
 lib/Makefile      |   1 +
 lib/test_printf.c | 362 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 lib/vsprintf.c    |  35 ++++--
 4 files changed, 389 insertions(+), 12 deletions(-)
 create mode 100644 lib/test_printf.c

-- 
2.1.3

--
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/