ISO 8601 format dates permit two different encodings of midnight - 00:00:00 and 24:00:00 - the first is midnight today and the second is midnight tomorrow and is exactly equivalent to the first with tomorrow's date.
Note that the implementation of mktime64() doesn't actually need to be changed to handle this - the multiplication by 3600 of the hour will take care of it automatically. However, we should document that this handling is done in mktime64() and is thus in a common place in the kernel. This handling is required for X.509 certificate parsing which can be given ISO 8601 dates. Signed-off-by: David Howells <dhowe...@redhat.com> cc: John Stultz <john.stu...@linaro.org> cc: Arnd Bergmann <a...@arndb.de> cc: sta...@vger.kernel.org --- kernel/time/time.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/kernel/time/time.c b/kernel/time/time.c index 1858b10602f5..56e7ada38471 100644 --- a/kernel/time/time.c +++ b/kernel/time/time.c @@ -326,6 +326,9 @@ EXPORT_SYMBOL(timespec_trunc); * A leap second can be indicated by calling this function with sec as * 60 (allowable under ISO 8601). The leap second is treated the same * as the preceding second since they don't exist in UNIX time. + * + * An encoding of midnight at the end of the day as 24:00:00 - ie. midnight + * tomorrow - (allowable under ISO 8601) is supported. */ time64_t mktime64(unsigned int year0, unsigned int mon0, unsigned int day, unsigned int hour, @@ -346,7 +349,7 @@ time64_t mktime64(unsigned int year0, unsigned int mon0, return ((((time64_t) (year/4 - year/100 + year/400 + 367*mon/12 + day) + year*365 - 719499 - )*24 + hour /* now have hours */ + )*24 + hour /* now have hours - midnight tomorrow handled here */ )*60 + min /* now have minutes */ )*60 + sec; /* finally seconds */ } -- To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html