diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2019-11-08 23:34:30 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-11-13 14:08:21 +0300 |
| commit | 998174042da229e2cf5841f574aba4a743e69650 (patch) | |
| tree | 7de3fb2f07a0b2dac31e43f55506c1cebf19f29e /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 01b59c763fe2de845b65900485b141fdd7bbf93e (diff) | |
| download | linux-998174042da229e2cf5841f574aba4a743e69650.tar.xz | |
ppdev: fix PPGETTIME/PPSETTIME ioctls
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.
Cc: stable@vger.kernel.org
Fixes: 3b9ab374a1e6 ("ppdev: convert to y2038 safe")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Link: https://lore.kernel.org/r/20191108203435.112759-8-arnd@arndb.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions