Messages in this thread | | | From | Arnd Bergmann <> | Date | Tue, 25 Apr 2017 22:31:15 +0200 | Subject | Re: [Y2038] [PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits |
| |
On Tue, Apr 25, 2017 at 10:02 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote: > On Tue, Apr 25, 2017 at 12:47 PM, Arnd Bergmann <arnd@arndb.de> wrote: >> >> There is one global option that I want to see, and that is for completely >> disabling all components that are known to be broken in y2038. > > I really don't see the point. > > Don't do it. Make it some local hack, I'm not taking crazy patches.
I have the local hack , and used it to find all the drivers that use a 32-bit time_t internally (and mark them with a Kconfig dependency for testing).
Would it be ok to have a simple way of removing the time_t definition (e.g. by passing '-DREQUIRE_TIME64' to the compiler, but without the Kconfig option? That way, someone who wants to ship a product can at least find the obvious dependencies on stuff that remains broken.
Arnd
| |