netdev - Re: [PATCH v2 net-next 3/6] sfc: optional logging of TC offload errors

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: <16da471c-076b-90b3-3935-abd31c6ef4d3@gmail.com>
Date:   Fri, 30 Sep 2022 10:03:01 +0100
From:   Edward Cree <ecree.xilinx@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     netdev@...r.kernel.org, linux-net-drivers@....com,
        davem@...emloft.net, pabeni@...hat.com, edumazet@...gle.com,
        habetsm.xilinx@...il.com
Subject: Re: [PATCH v2 net-next 3/6] sfc: optional logging of TC offload
 errors

On 29/09/2022 02:15, Jakub Kicinski wrote:
> Hm. I wonder if throwing a tracepoint into the extack setting
> machinery would be a reasonable stop gap for debugging.

It has one (do_trace_netlink_extack()), but sadly that won't play
 so well with formatted extacks since AIUI trace needs a constant
 string (I'm just giving it the format string in my prototype).
But yeah it's better than nothing.