On Monday 19 October 2015 11:53:25 John Stultz wrote: > > But yea. At the same time I get you want to avoid user-pain like in > the case of the badly initialized RTC, but in that case would > returning 0 for RTC reads greater then y2038 on 32 bit systems be a > more sane fix? I like that idea. In theory we could go further and check that the RTC is somewhere between 2015 and 2037 (or higher on 64-bit systems) but return 0 (1970) for anything that is outside of that range. That might have side-effects for users that have a legitimate reason to backdate their clocks though. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
