Re: [PATCH 3/6] security: Introduce security_settime64()

On 15 July 2015 at 18:24, Thomas Gleixner wrote: > On Wed, 15 Jul 2015, Baolin Wang wrote: > >> security_settime() returns a timespec, which is not year 2038 safe > > It returns int, which is year 2038 safe on all systems. Copy and paste > is great, right? > Sorry, will fix that. >> -int securit

Re: [PATCH 3/6] security: Introduce security_settime64()

On Wed, 15 Jul 2015, Baolin Wang wrote: > security_settime() returns a timespec, which is not year 2038 safe It returns int, which is year 2038 safe on all systems. Copy and paste is great, right? > -int security_settime(const struct timespec *ts, const struct timezone *tz); > +int security_sett

[PATCH 3/6] security: Introduce security_settime64()

security_settime() returns a timespec, which is not year 2038 safe on 32bit systems. Thus this patch introduces the security_settime64() function with timespec64 type. We also convert the cap_settime() helper function to use the 64bit types. Signed-off-by: Baolin Wang --- include/linux/lsm_hook