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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 16 Jan 2021 16:09:48 -0600 From: Timur Tabi <timur@...nel.org> To: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Petr Mladek <pmladek@...e.com>, roman.fietze@...na.com, keescook@...omium.org, Steven Rostedt <rostedt@...dmis.org>, John Ogness <john.ogness@...utronix.de>, linux-mm@...ck.org, Akinobu Mita <akinobu.mita@...il.com> Subject: [PATCH 0/2] introduce DUMP_PREFIX_UNHASHED for hex dumps First patch updates print_hex_dump() and related functions to allow callers to print hex dumps with unhashed addresses. It adds a new prefix type, so existing code is unchanged. Second patch changes a page poising function to use the new address type. This is just an example of a change. If it's wrong, it doesn't need to be applied. IMHO, hashed addresses make very little sense for hex dumps, which print addresses in 16- or 32-byte increments. Typical use-case is to correlate an addresses in between one of these increments with some other address, but that can't be done if the addresses are hashed. I expect most developers to want to replace their usage of DUMP_PREFIX_ADDRESS with DUMP_PREFIX_UNHASHED, now that they have the opportunity. Timur Tabi (2): [v2] lib/hexdump: introduce DUMP_PREFIX_UNHASHED for unhashed addresses mm/page_poison: use unhashed address in hexdump for check_poison_mem() fs/seq_file.c | 3 +++ include/linux/printk.h | 8 +++++--- lib/hexdump.c | 9 +++++++-- lib/seq_buf.c | 9 +++++++-- mm/page_poison.c | 2 +- 5 files changed, 23 insertions(+), 8 deletions(-) -- 2.25.1
Powered by blists - more mailing lists