lkml.org 
[lkml]   [2019]   [Jan]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [PATCH v2 28/29] y2038: rename old time and utime syscalls
    On Fri, Jan 18, 2019 at 5:21 PM Arnd Bergmann <arnd@arndb.de> wrote:
    > The time, stime, utime, utimes, and futimesat system calls are only
    > used on older architectures, and we do not provide y2038 safe variants
    > of them, as they are replaced by clock_gettime64, clock_settime64,
    > and utimensat_time64.
    >
    > However, for consistency it seems better to have the 32-bit architectures
    > that still use them call the "time32" entry points (leaving the
    > traditional handlers for the 64-bit architectures), like we do for system
    > calls that now require two versions.
    >
    > Note: We used to always define __ARCH_WANT_SYS_TIME and
    > __ARCH_WANT_SYS_UTIME and only set __ARCH_WANT_COMPAT_SYS_TIME and
    > __ARCH_WANT_SYS_UTIME32 for compat mode on 64-bit kernels. Now this is
    > reversed: only 64-bit architectures set __ARCH_WANT_SYS_TIME/UTIME, while
    > we need __ARCH_WANT_SYS_TIME32/UTIME32 for 32-bit architectures and compat
    > mode. The resulting asm/unistd.h changes look a bit counterintuitive.
    >
    > This is only a cleanup patch and it should not change any behavior.
    >
    > Signed-off-by: Arnd Bergmann <arnd@arndb.de>

    > arch/m68k/include/asm/unistd.h | 4 ++--
    > arch/m68k/kernel/syscalls/syscall.tbl | 10 +++++-----

    For m68k:
    Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

    Gr{oetje,eeting}s,

    Geert


    --
    Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

    In personal conversations with technical people, I call myself a hacker. But
    when I'm talking to journalists I just say "programmer" or something like that.
    -- Linus Torvalds

    \
     
     \ /
      Last update: 2019-01-21 09:57    [W:3.815 / U:0.208 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site