[Top] [All Lists]

Re: [PATCH v3 0/8] net: y2038-safe socket timestamps

To: Deepa Dinamani <>
Subject: Re: [PATCH v3 0/8] net: y2038-safe socket timestamps
From: Willem de Bruijn <>
Date: Tue, 8 Jan 2019 08:37:07 -0500
Cc: David Miller <>, LKML <>, Network Development <>, Arnd Bergmann <>, y2038 Mailman List <>, Chris Zankel <>, Helge Deller <>, David Howells <>,,, "James E.J. Bottomley" <>,,,,, "open list:RALINK MIPS ARCHITECTURE" <>, Parisc List <>,, linux-s390 <>,, Ralf Baechle <>,,, sparclinux <>, Thomas Gleixner <>,
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6nXKYaCNiwgzlBrCj/v1vQjps+Q5gGfbpQOOfB1h0CI=; b=fQJq3kfazkRaVcWp/jPyOlyKRy5/ek8ymQOV+bF2CWzmEjQUp053C+Rgi/qmTgxPb7 2AiGxr0nOB+Osg6yaSWO3EoPyW8btVIJDxvZFk211tKdiHLhXICxYKURjEUDjgR7c3BE 7Pp4d7Xkb5SUpz066jZZ2OK6w4qtdfNP1XPUF6fdNqJaFMdtIPVyBBJnj6IhiQy0AA0J LgUa75e0kK/DymYavwYIg7nKGj40aqv0rcaDgdYAQ4yzXboZqTFPtvglQgYIV330GHm3 h8ksU4gM3pO1YNzJtUYRdWDMnVwaJFqz2iTO6DL8UfDPpefn0sVNG2l24PFVvS8EM4NK ChUw==
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
References: <>
On Mon, Jan 7, 2019 at 10:29 PM Deepa Dinamani <> wrote:
> The series introduces new socket timestamps that are
> y2038 safe.
> The time data types used for the existing socket timestamp
> are not y2038 safe. The series introduces SO_TIMESTAMP_NEW,
> These new timestamps can be used on all architectures.
> The alternative considered was to extend the sys_setsockopt()
> by using the flags. We did not receive any strong opinions about
> either of the approaches. Hence, this was chosen, as glibc folks
> preferred this.
> The series does not deal with updating the internal kernel socket
> calls like rxrpc to make them y2038 safe. This will be dealt
> with separately.
> Note that the timestamps behavior already does not match the
> man page specific behavior:
>     This ioctl should only be used if the socket option SO_TIMESTAMP
>         is not set on the socket. Otherwise, it returns the timestamp of
>         the last packet that was received while SO_TIMESTAMP was not set,
>         or it fails if no such packet has been received,
>         (i.e., ioctl(2) returns -1 with errno set to ENOENT).
> The recommendation is to update the man page to remove the above statement.
> The overview of the series is as below:
> 1. Delete asm specific socket.h when possible.
> 2. Support SO/SCM_TIMESTAMP* options only in userspace.
> 3. Alter socket options so that SOCK_RCVTSTAMPNS does
>    not rely on SOCK_RCVTSTAMP.
> 4. Introduce y2038 safe types for socket timestamp.
> 5. Introduce new y2038 safe socket options SO/SCM_TIMESTAMP*_NEW.
> Changes since v2:
> * Removed extra functions to reduce diff churn as per code review

Thanks, Deepa. This set looks great to me.

One issue, it does not apply cleanly to current davem-net-next/master
for me. A conflict on patch 7. It does apply cleanly on davem-net
master. Please rebase and also send with [PATCH net-next].

Perhaps also run the selftests in
tools/testing/selftests/networking/timestamping/, just
to be sure.

Since you have a to resend anyway, a few minor nits inline, as well.

<Prev in Thread] Current Thread [Next in Thread>