On Mon, Jan 7, 2019 at 10:29 PM Deepa Dinamani <deepa.ker...@gmail.com> wrote:
>
> Add SO_TIMESTAMP_NEW and SO_TIMESTAMPNS_NEW variants of
> socket timestamp options.
> These are the y2038 safe versions of the SO_TIMESTAMP_OLD
> and SO_TIMESTAMPNS_OLD for all architectures.
>
> Note that the format of scm_timestamping.ts[0] is not changed
> in this patch.
>
> Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com>
> Cc: j...@parisc-linux.org
> Cc: r...@linux-mips.org
> Cc: r...@twiddle.net
> Cc: linux-al...@vger.kernel.org
> Cc: linux-m...@linux-mips.org
> Cc: linux-par...@vger.kernel.org
> Cc: linux-r...@vger.kernel.org
> Cc: netdev@vger.kernel.org
> Cc: sparcli...@vger.kernel.org
> @@ -1864,20 +1864,39 @@ static void tcp_update_recv_tstamps(struct sk_buff
> *skb,
> static void tcp_recv_timestamp(struct msghdr *msg, const struct sock *sk,
> struct scm_timestamping *tss)
> {
> - struct __kernel_old_timeval tv;
> bool has_timestamping = false;
> + int new_tstamp = sock_flag(sk, SOCK_TSTAMP_NEW);
nit: move above has_timestamping to maintain reverse christmas tree ordering
