netdev - [PATCH net-next 0/2] Transmit time stamping on tun/tap interfaces

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]

Message-Id: <cover.1374254757.git.richardcochran@gmail.com>
Date:	Fri, 19 Jul 2013 19:40:08 +0200
From:	Richard Cochran <richardcochran@...il.com>
To:	<netdev@...r.kernel.org>
Cc:	David Miller <davem@...emloft.net>,
	"Michael S. Tsirkin" <mst@...hat.com>
Subject: [PATCH net-next 0/2] Transmit time stamping on tun/tap interfaces

This series adds transmit SO_TIMESTAMPING for tun and tap devices.
Having this support is useful for testing multiple instances of PTP
programs (for example, to exercise the best master clock behavior)
and for synchronizing virtual guests.

The first patch refactors the code that delivers raw error queue
packets into a common function, in order to avoid multiple, nearly
identical implementations. This can be used whenever a network layer
has an error queue for transmit time stamp reporting only.

Thanks,
Richard

Richard Cochran (2):
  Provide a generic socket error queue delivery method for Tx time
    stamps.
  tun: Support software transmit time stamping.

 drivers/net/tun.c           |   14 +++++++++++--
 include/net/sock.h          |    2 ++
 include/uapi/linux/if_tun.h |    3 +++
 net/core/sock.c             |   47 ++++++++++++++++++++++++++++++++++++++++++
 net/packet/af_packet.c      |   48 ++-----------------------------------------
 5 files changed, 66 insertions(+), 48 deletions(-)

-- 
1.7.10.4

--
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