netdev - Re: [net-next 0/4] remove deprecated syststamp

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: <20140729.114044.377340575518627384.davem@davemloft.net>
Date:	Tue, 29 Jul 2014 11:40:44 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	willemb@...gle.com
Cc:	netdev@...r.kernel.org, richardcochran@...il.com,
	kreese@...iumnetworks.com, ddaney@...iumnetworks.com,
	dborkman@...hat.com, jdmason@...zu.us
Subject: Re: [net-next 0/4] remove deprecated syststamp

From: Willem de Bruijn <willemb@...gle.com>
Date: Fri, 25 Jul 2014 18:01:28 -0400

> The network stack can generate two kinds of hardware timestamps:
> - hwtstamp stores a hw timestamp in device-specific raw format
> - syststamp convers the raw format to system time
> 
> The second is deprecated and only implemented by a single device
> driver. The suggested alternative is to communicate hwtstamp +
> directly expose the NIC PTP clock device through ptp_clock_info.
> The remaining driver (octeon) does not expose such a standard
> interface as of now. It does have its own PTP library that depends
> on its own shared memory PTP clock interface.
> 
> This patchset
> 1. reverts the syststamp code in the one driver (octeon)
> 2. reverts an unnecessary zero initialization in another (vxge)
> 3. modifies PF_PACKET to use syststamp is != 0 (because always == 0)
> 4. modifies SCM_TIMESTAMPING in the same way
> 
> For backwards compatibility, the interfaces are not removed.
> Applications can still request SOF_TIMESTAMPING_SYS_HARDWARE. The
> response field in scm_timestamping also remains. As was the case
> for hardware/drivers that did not implement the feature, the
> setsockopt succeeds, but the response field is always zero.

Series applied, thanks Willem.
--
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