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]
Message-ID: <Pine.LNX.4.64.1406031427130.12421@digraph.polyomino.org.uk>
Date:	Tue, 3 Jun 2014 14:33:10 +0000
From:	"Joseph S. Myers" <joseph@...esourcery.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	"H. Peter Anvin" <hpa@...or.com>, <linux-kernel@...r.kernel.org>,
	<linux-arch@...r.kernel.org>, <john.stultz@...aro.org>,
	<hch@...radead.org>, <tglx@...utronix.de>, <geert@...ux-m68k.org>,
	<lftan@...era.com>, <linux-fsdevel@...r.kernel.org>,
	<ceph-devel@...r.kernel.org>, <cluster-devel@...hat.com>,
	<coda@...cmu.edu>, <codalist@...emann.coda.cs.cmu.edu>,
	<fuse-devel@...ts.sourceforge.net>,
	<linux-afs@...ts.infradead.org>, <linux-btrfs@...r.kernel.org>,
	<linux-cifs@...r.kernel.org>, <linux-ext4@...r.kernel.org>,
	<linux-f2fs-devel@...ts.sourceforge.net>,
	<linux-mtd@...ts.infradead.org>, <linux-nfs@...r.kernel.org>,
	<linux-ntfs-dev@...ts.sourceforge.net>,
	<linux-scsi@...r.kernel.org>, <logfs@...fs.org>,
	<ocfs2-devel@....oracle.com>, <reiserfs-devel@...r.kernel.org>,
	<samba-technical@...ts.samba.org>, <xfs@....sgi.com>
Subject: Re: [RFC 00/32] making inode time stamps y2038 ready

On Tue, 3 Jun 2014, Arnd Bergmann wrote:

> I think John Stultz and Thomas Gleixner have already started looking
> at how the timekeeping code can be updated. Once that is done, we should
> be able to add a functional 64-bit gettimeofday/settimeofday syscall
> pair. While I definitely agree this is one of the most basic things to
> have, it's also not an area of the kernel that is easy to change.

64-bit clock_gettime / clock_settime instead of gettimeofday / 
settimeofday should avoid the need for the kernel to have a 64-bit version 
of struct timeval.  (Userspace 64-bit gettimeofday / settimeofday would 
need to use a combination of the syscalls if the tz pointer is non-NULL.)

-- 
Joseph S. Myers
joseph@...esourcery.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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ