netdev - Re: [PATCH net-next v2 2/2] net: make SOF_TIMESTAMPING_RX

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] [day] [month] [year] [list]

Message-ID: <20240829191435.739154ef@kernel.org>
Date: Thu, 29 Aug 2024 19:14:35 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jason Xing <kerneljasonxing@...il.com>
Cc: davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
 dsahern@...nel.org, willemb@...gle.com, netdev@...r.kernel.org, Jason Xing
 <kernelxing@...cent.com>, Willem de Bruijn
 <willemdebruijn.kernel@...il.com>
Subject: Re: [PATCH net-next v2 2/2] net: make SOF_TIMESTAMPING_RX_SOFTWARE
 feature per socket

On Fri, 30 Aug 2024 08:40:47 +0800 Jason Xing wrote:
> In this case, we expect to control whether we can report the rx
> timestamp in this function. But we also need to handle the egress
> path, or else reporting the tx timestamp will fail. Egress path and
> ingress path will finally call sock_recv_timestamp(). We have to
> distinguish them. Errqueue is a good indicator to reflect the flow
> direction.

That is better, FWIW, thanks