From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f171.google.com ([209.85.216.171]:41171 "EHLO mail-qt0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726845AbeINVWI (ORCPT ); Fri, 14 Sep 2018 17:22:08 -0400 MIME-Version: 1.0 References: <20180901204721.13117-1-deepa.kernel@gmail.com> In-Reply-To: <20180901204721.13117-1-deepa.kernel@gmail.com> From: Arnd Bergmann Date: Fri, 14 Sep 2018 18:06:42 +0200 Message-ID: Subject: Re: [PATCH 0/5] y2038: Make ppoll, io_pgetevents and pselect y2038 safe To: Deepa Dinamani Cc: Al Viro , Thomas Gleixner , Linux Kernel Mailing List , y2038 Mailman List , Linux FS-devel Mailing List , Linux API , linux-aio Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, Sep 1, 2018 at 10:48 PM Deepa Dinamani wrote: > > The series transitions the ppoll, io_getevents, and pselect syscalls > to be y2038 safe. > > This is part of the work proceeding for syscalls for y2038. > It is based on the series [1] from Arnd Bergmann. > > The overview of the series is as below: > 1. Refactor sigmask handling logic for the above syscalls. > 2. Provide y2038 safe versions of syscalls for all ABIs. > > [1] https://lkml.org/lkml/2018/8/27/651 Hi Deepa, This is a very nice series, sorry for taking way too long before I had a good look at it. The first two patches in particular are great. The third patch looks like it has a small bug that I commented on, but given how much more thought you have put into this than I did, it's just as possible that I misunderstood it. I've applied you series locally now, but have not pushed it out yet for linux-next because of that one issue. I'll send a pull request to Thomas for my other patches for now, and a follow-up with these once we have clarified it. Arnd