netdev - Re: [PATCH net-next RFC] Dump SW SQ context as part of tx reporter

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]

Date:   Tue, 30 Apr 2019 11:26:49 +0000
From:   Aya Levin <ayal@...lanox.com>
To:     Jakub Kicinski <jakub.kicinski@...ronome.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Eran Ben Elisha <eranbe@...lanox.com>,
        Saeed Mahameed <saeedm@...lanox.com>,
        Jiri Pirko <jiri@...lanox.com>
Subject: Re: [PATCH net-next RFC] Dump SW SQ context as part of tx reporter



On 4/30/2019 3:54 AM, Jakub Kicinski wrote:
> On Mon, 29 Apr 2019 17:17:39 +0300, Aya Levin wrote:
>> In order to offline translate the raw memory into a human readable
>> format, the user can use some out-of-kernel scripts which receives as an
>> input the following:
>> - Object raw memory
>> - Driver object compiled with debug info (can be taken/generated at any time from the machine)
>> - Object name
> 
> Nice!  IMHO this is more clean, precise and scalable than the fmsg stuff
> that we have now.
> 
> Would you mind taking the string identifiers down a little bit more?
> "memory" could just have a first-class netlink attribute, it doesn't
> have to be this fake JSON string pair..
> 
Thanks!
I am still using fmsg which is the API to construct JSON like output. 
The fmg object contains the raw data.
I like your idea to remove the memory tag and just leave the array of 
byte arrays. The SW dump devlink output without scripting is meaningless.