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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 20 Sep 2021 10:20:33 -0700
From:   Cong Wang <>
To:     Steven Rostedt <>
Cc:     Zhongya Yan <>,
        Eric Dumazet <>,
        Brendan Gregg <>,
        Linux Kernel Network Developers <>,
        LKML <>,
        Jakub Kicinski <>,
        Ingo Molnar <>,
        David Miller <>,
        Hideaki YOSHIFUJI <>,
        David Ahern <>, Yonghong Song <>,
        Zhongya Yan <>
Subject: Re: [PATCH] tcp: tcp_drop adds `SNMP` and `reason` parameter for tracing

On Mon, Sep 20, 2021 at 10:15 AM Steven Rostedt <> wrote:
> On Mon, 20 Sep 2021 09:54:02 -0700
> Cong Wang <> wrote:
> > Also, kernel does not have to explain it in strings, those SNMP
> > counters are already available for user-space, so kernel could
> > just use SNMP enums and let user-space interpret them. In many
> > cases, you are just adding strings for those SNMP enums.
> The strings were requested by the networking maintainers.

I think you misunderstand my point. Eric's point is hex address
vs. string, which I never disagree. With SNMP enum, user-space
can easily interpret it to string too, so at the end you still get strings
but not from kernel. This would at least save a handful of strings
from vmlinux, especially if we expand it beyond TCP.


Powered by blists - more mailing lists