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
| ||
|
Date: Tue, 15 Nov 2022 10:14:44 +0100 From: Paolo Abeni <pabeni@...hat.com> To: Peilin Ye <yepeilin.cs@...il.com>, Eric Dumazet <edumazet@...gle.com>, "David S. Miller" <davem@...emloft.net>, Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>, David Ahern <dsahern@...nel.org>, Jakub Kicinski <kuba@...nel.org> Cc: Peilin Ye <peilin.ye@...edance.com>, Cong Wang <cong.wang@...edance.com>, Leon Romanovsky <leon@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next v6] net/sock: Introduce trace_sk_data_ready() Hello, On Wed, 2022-11-09 at 18:34 -0800, Peilin Ye wrote: > As suggested by Cong, introduce a tracepoint for all ->sk_data_ready() > callback implementations. For example: > > <...> > ksoftirqd/0-16 [000] ..s.. 99.784482: sk_data_ready: family=10 protocol=58 func=sock_def_readable > ksoftirqd/0-16 [000] ..s.. 99.784819: sk_data_ready: family=10 protocol=58 func=sock_def_readable > <...> It looks like this does not touch/include sk_psock_strp_data_ready(), why? thanks! Paolo
Powered by blists - more mailing lists