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-next>] [day] [month] [year] [list]
Date:   Mon, 6 Mar 2023 07:47:02 -0500
From:   Alexander Aring <aahringo@...hat.com>
To:     peilin.ye@...edance.com
Cc:     cong.wang@...edance.com, "David S. Miller" <davem@...emloft.net>,
        Network Development <netdev@...r.kernel.org>,
        cluster-devel <cluster-devel@...hat.com>
Subject: introduce function wrapper for sk_data_ready() call?

Hi,

I saw that in 6.3-rc1 the following patch introduced something in dlm
socket application handling 40e0b0908142 ("net/sock: Introduce
trace_sk_data_ready()"). I am asking myself if we could instead
introduce a wrapper in net/ protocol family implementations and they
do such trace event calls there inside the socket implementation
instead of letting the application layer do it. It looks pretty
generic for me and it does not trace any application specific
information.

I did something similar for sk_error_report(), see e3ae2365efc1 ("net:
sock: introduce sk_error_report").

Thanks.

- Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ