Re: [Y2038] [PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits

2017-04-25 Thread Arnd Bergmann
On Tue, Apr 25, 2017 at 10:35 PM, Linus Torvalds wrote: > On Tue, Apr 25, 2017 at 1:31 PM, Arnd Bergmann wrote: >> >> 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

Re: [Y2038] [PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits

2017-04-25 Thread Linus Torvalds
On Tue, Apr 25, 2017 at 1:31 PM, Arnd Bergmann wrote: > > 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 dep

Re: [Y2038] [PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits

2017-04-25 Thread Arnd Bergmann
On Tue, Apr 25, 2017 at 10:02 PM, Linus Torvalds wrote: > On Tue, Apr 25, 2017 at 12:47 PM, Arnd Bergmann 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. > >

Re: [PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits

2017-04-25 Thread Linus Torvalds
On Tue, Apr 25, 2017 at 12:47 PM, Arnd Bergmann 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.

Re: [PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits

2017-04-25 Thread Arnd Bergmann
On Sun, Apr 9, 2017 at 4:58 AM, Deepa Dinamani wrote: >>> Allow read only mounts for filesystems that do not >>> have maximum timestamps beyond the y2038 expiry >>> timestamp. >> >> This option seems arbitrary and pointless. >> >> Nobody sane should ever enable it except for testing, but for testi

Re: [PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits

2017-04-08 Thread Deepa Dinamani
>> Allow read only mounts for filesystems that do not >> have maximum timestamps beyond the y2038 expiry >> timestamp. > > This option seems arbitrary and pointless. > > Nobody sane should ever enable it except for testing, but for testing > it would be much better to simply specify what the limit

Re: [PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits

2017-04-08 Thread Linus Torvalds
On Sat, Apr 8, 2017 at 12:37 PM, Deepa Dinamani wrote: > Allow read only mounts for filesystems that do not > have maximum timestamps beyond the y2038 expiry > timestamp. This option seems arbitrary and pointless. Nobody sane should ever enable it except for testing, but for testing it would be

[PATCH v5 2/5] vfs: Add checks for filesystem timestamp limits

2017-04-08 Thread Deepa Dinamani
Allow read only mounts for filesystems that do not have maximum timestamps beyond the y2038 expiry timestamp. Also, allow a sysctl override to all such filesystems to be mounted with write permissions. A boot param supports initial override of these checks from the early boot without recompilation