netdev - Storing hardware timestamps - how about using the new skb's control block?

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:	Wed, 12 Nov 2008 07:23:40 +1030
From:	Mark Smith 
	<nanog@...5b20a518b8f6864949bd940457dc124746ddc.nosense.org>
To:	patrick.ohly@...el.com
Cc:	netdev@...r.kernel.org
Subject: Storing hardware timestamps - how about using the new skb's control
 block?

Hi,

Just a quick suggestion for storing hardware timestamps, how about
storing them in the new skb's control block?

>From what I understand, any private users of the control block are
supposed to ignore the existing value, and if a protocol/tap is going
to be looking at the new skb, it should have done a skb_share_check()
first to grab it's own private copy if necessary, protecting the
control block stored timestamp value from any of the other skb
users who might change the control block value for their own purposes.

Regards,
Mark.

-- 

        "Sheep are slow and tasty, and therefore must remain constantly
         alert."
                                   - Bruce Schneier, "Beyond Fear"
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html