Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20211007123147.5780-1-rpalethorpe@suse.com> <20211007123147.5780-2-rpalethorpe@suse.com>
In-Reply-To: <20211007123147.5780-2-rpalethorpe@suse.com>
From:   Arnd Bergmann <arnd@arndb.de>
Date:   Thu, 7 Oct 2021 14:53:35 +0200
Message-ID: <CAK8P3a0BiS=mOxS8FeJnxz7pjWFuVNJz0WPFVVEPzsZ0bmzYkQ@mail.gmail.com>
Subject: Re: [PATCH v2 2/2] vsock: Enable y2038 safe timeval for timeout
To:     Richard Palethorpe <rpalethorpe@suse.com>
Cc:     Arnd Bergmann <arnd@arndb.de>,
        "David S. Miller" <davem@davemloft.net>,
        Jakub Kicinski <kuba@kernel.org>,
        Stefano Garzarella <sgarzare@redhat.com>,
        Andra Paraschiv <andraprs@amazon.com>,
        Eric Dumazet <edumazet@google.com>,
        Arseny Krasnov <arseny.krasnov@kaspersky.com>,
        Willem de Bruijn <willemb@google.com>,
        Deepa Dinamani <deepa.kernel@gmail.com>,
        Networking <netdev@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Richard Palethorpe <rpalethorpe@richiejp.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Oct 7, 2021 at 2:34 PM Richard Palethorpe <rpalethorpe@suse.com> wrote:
>
> Reuse the timeval compat code from core/sock to handle 32-bit and
> 64-bit timeval structures. Also introduce a new socket option define
> to allow using y2038 safe timeval under 32-bit.
>
> The existing behavior of sock_set_timeout and vsock's timeout setter
> differ when the time value is out of bounds. vsocks current behavior
> is retained at the expense of not being able to share the full
> implementation.
>
> This allows the LTP test vsock01 to pass under 32-bit compat mode.
>
> Fixes: fe0c72f3db11 ("socket: move compat timeout handling into sock.c")
> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
> Cc: Richard Palethorpe <rpalethorpe@richiejp.com>

I had a look to make sure you've covered all the tricky corner cases,

Reviewed-by: Arnd Bergmann <arnd@arndb.de>