[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3vEBepxkP-UmcpHHqrpq2m3woxyxVf2DSL125UYb9Ktg@mail.gmail.com>
Date: Thu, 21 Nov 2019 15:06:39 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Ben Hutchings <ben.hutchings@...ethink.co.uk>
Cc: y2038 Mailman List <y2038@...ts.linaro.org>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Michael S. Tsirkin" <mst@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"# 3.4.x" <stable@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Bamvor Jian Zhang <bamvor.zhangjian@...aro.org>
Subject: Re: [Y2038] [PATCH 7/8] ppdev: fix PPGETTIME/PPSETTIME ioctls
On Wed, Nov 20, 2019 at 8:29 PM Ben Hutchings
<ben.hutchings@...ethink.co.uk> wrote:
>
> On Fri, 2019-11-08 at 21:34 +0100, Arnd Bergmann wrote:
> > Going through the uses of timeval in the user space API,
> > I noticed two bugs in ppdev that were introduced in the y2038
> > conversion:
> >
> > * The range check was accidentally moved from ppsettime to
> > ppgettime
> >
> > * On sparc64, the microseconds are in the other half of the
> > 64-bit word.
> >
> > Fix both, and mark the fix for stable backports.
>
> Like the patch for lpdev, this also doesn't completely fix sparc64.
I think the same applies as in the other patch:
- it actually works correctly because of the alignment
- it's already merged in linux-next
- if you wish, I can add another cleanup patch on top, but I'd
prefer to just leave it as it is.
Arnd
Powered by blists - more mailing lists