[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180717125039.GB25416@infradead.org>
Date: Tue, 17 Jul 2018 05:50:39 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: tglx@...utronix.de, y2038@...ts.linaro.org, hch@...radead.org,
linux-api@...r.kernel.org, linux-arch@...r.kernel.org,
libc-alpha@...rceware.org, albert.aribaud@...ev.fr,
netdev@...r.kernel.org, viro@...iv.linux.org.uk,
peterz@...radead.org, dvhart@...radead.org, ebiederm@...ssion.com,
linux@...inikbrodowski.net
Subject: Re: [PATCH v2 02/17] y2038: Remove newstat family from default
syscall set
On Mon, Jul 16, 2018 at 06:10:48PM +0200, Arnd Bergmann wrote:
> We have four generations of stat() syscalls:
> - the oldstat syscalls that are only used on the older architectures
> - the newstat family that is used on all 64-bit architectures but
> lacked support for large files on 32-bit architectures.
> - the stat64 family that is used mostly on 32-bit architectures to
> replace newstat
> - statx() to replace all of the above, adding 64-bit timestamps among
> other things.
>
> We already compile stat64 only on those architectures that need it,
> but newstat is always built, including on those that don't reference
> it. This adds a new __ARCH_WANT_NEW_STAT symbol along the lines of
> __ARCH_WANT_OLD_STAT and __ARCH_WANT_STAT64 to control compilation of
> newstat. All architectures that need it use an explict define, the
> others now get a little bit smaller, and future architecture (including
> 64-bit targets) won't ever see it.
>
> Acked-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
Do I read this right that you only want to provide statx by default?
It is a little different from the traditional stat calls, so I'd like
to know this is actually ok from libc folks first.
Powered by blists - more mailing lists