linux-kernel - Re: [PATCH v2 0/4] printf: Add struct range print specifier

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: <18854680-4ab7-4453-85ff-78351d4d4ec9@gmx.de>
Date: Wed, 30 Oct 2024 11:51:54 +0100
From: metux <metux@....de>
To: Ira Weiny <ira.weiny@...el.com>, Andrew Morton
 <akpm@...ux-foundation.org>, Petr Mladek <pmladek@...e.com>,
 Steven Rostedt <rostedt@...dmis.org>,
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 Rasmus Villemoes <linux@...musvillemoes.dk>,
 Sergey Senozhatsky <senozhatsky@...omium.org>,
 Jonathan Corbet <corbet@....net>, Davidlohr Bueso <dave@...olabs.net>,
 Jonathan Cameron <jonathan.cameron@...wei.com>,
 Dave Jiang <dave.jiang@...el.com>,
 Alison Schofield <alison.schofield@...el.com>,
 Vishal Verma <vishal.l.verma@...el.com>,
 Dan Williams <dan.j.williams@...el.com>
Cc: Fan Ni <fan.ni@...sung.com>, Bagas Sanjaya <bagasdotme@...il.com>,
 linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-cxl@...r.kernel.org
Subject: Re: [PATCH v2 0/4] printf: Add struct range print specifier

On 26.10.24 02:46, Ira Weiny wrote:
> Support for the Compute Express Link (CXL) Dynamic Capacity Devices
> (DCD) have grown a number of uses to print struct range.[1]  Support for
> a printf specifier '%pra' was being worked within a large series and has
> garnered a number of comments and discussion.

This is just printing out hex dump of a memory range, correct ?

What I'm looking for quite some time is a sane way for dumping structs
in a human readable form (field: value pairs, using their actual types
eg. int vs string, ...).

Any idea to do that in a generic way ?
(potentially using debug info ?)


--mtx