linux-kernel - [PATCH v2 0/2] lib/vsprintf: introduce stricter rules for %p extensions

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:	Tue, 29 Dec 2015 18:42:36 +0200
From:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Rasmus Villemoes <linux@...musvillemoes.dk>,
	linux-kernel@...r.kernel.org, Joe Perches <joe@...ches.com>
Cc:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: [PATCH v2 0/2] lib/vsprintf: introduce stricter rules for %p extensions

Besides the code refactoring we introduce the following rules for %p extensions
here. i.e:

- fixed type extensions are always printed in hex format, prefixed by '0x',
  small letters, full field width on a running architecture (%pa[dp], %pNF)

- fallback to %p based on different kernel configuration will be under the same
  rule set as for fixed types above (%pCn when COMMON_CLK=n, %p[FfSsB] when
  KALLSYMS=n)

- fallback to %p of unimplemented extension will be under the same rule set as
  for fixed types above (%pN)

Since v1:
 - address comments from Joe and Rasmums (might be not all of them)
 - add patch 2
 - desribe in cover letter what is done besides refactoring

Andy Shevchenko (2):
  lib/vsprintf: refactor duplicate code to special_hex_number()
  lib/vsprintf: factor out %pN[F] handler as netdev_bits()

 lib/vsprintf.c | 70 ++++++++++++++++++++++++++++++++--------------------------
 1 file changed, 39 insertions(+), 31 deletions(-)

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