linux-kernel - Re: [PATCH v2 3/5] security: Introduce security

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Jul 2015 18:23:18 +1000 (AEST)
From:	James Morris <jmorris@...ei.org>
To:	Baolin Wang <baolin.wang@...aro.org>
cc:	serge.hallyn@...onical.com, arnd@...db.de, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, james.l.morris@...cle.com,
	serge@...lyn.com, paul@...l-moore.com, john.johansen@...onical.com,
	sds@...ho.nsa.gov, casey@...aufler-ca.com,
	penguin-kernel@...ove.SAKURA.ne.jp, neilb@...e.de,
	edumazet@...gle.com, jlayton@...marydata.com,
	linux-security-module@...r.kernel.org, y2038@...ts.linaro.org
Subject: Re: [PATCH v2 3/5] security: Introduce security_settime64()

On Wed, 29 Jul 2015, Baolin Wang wrote:

> security_settime() uses 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.
> 
> Move the security_settime() to the head file as a inline function for
> removing that inline helper when following up patches are fixed the
> call sites.
> 
> None of the existing hooks is using the timespec argument and therefor
> the patch is not doing any functional changes.
> 
> Signed-off-by: Baolin Wang <baolin.wang@...aro.org>

Reviewed-by: James Morris <james.l.morris@...cle.com>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/