[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a0BiS=mOxS8FeJnxz7pjWFuVNJz0WPFVVEPzsZ0bmzYkQ@mail.gmail.com>
Date: Thu, 7 Oct 2021 14:53:35 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Richard Palethorpe <rpalethorpe@...e.com>
Cc: Arnd Bergmann <arnd@...db.de>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Stefano Garzarella <sgarzare@...hat.com>,
Andra Paraschiv <andraprs@...zon.com>,
Eric Dumazet <edumazet@...gle.com>,
Arseny Krasnov <arseny.krasnov@...persky.com>,
Willem de Bruijn <willemb@...gle.com>,
Deepa Dinamani <deepa.kernel@...il.com>,
Networking <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Richard Palethorpe <rpalethorpe@...hiejp.com>
Subject: Re: [PATCH v2 2/2] vsock: Enable y2038 safe timeval for timeout
On Thu, Oct 7, 2021 at 2:34 PM Richard Palethorpe <rpalethorpe@...e.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@...e.com>
> Cc: Richard Palethorpe <rpalethorpe@...hiejp.com>
I had a look to make sure you've covered all the tricky corner cases,
Reviewed-by: Arnd Bergmann <arnd@...db.de>
Powered by blists - more mailing lists