linux-kernel - Re: [RFC 00/32] making inode time stamps y2038 ready

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.1406021350030.19591@digraph.polyomino.org.uk>
Date:	Mon, 2 Jun 2014 13:52:19 +0000
From:	"Joseph S. Myers" <joseph@...esourcery.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	<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>,
	<hpa@...or.com>, <linux-fsdevel@...r.kernel.org>,
	<ceph-devel@...r.kernel.org>, <cluster-devel@...hat.com>,
	<coda@...cmu.edu>, <codalist@...a.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 Fri, 30 May 2014, Arnd Bergmann wrote:

> a) is this the right approach in general? The previous discussion
>    pointed this way, but there may be other opinions.

The syscall changes seem like the sort of thing I'd expect, although 
patches adding new syscalls or otherwise affecting the kernel/userspace 
interface (as opposed to those relating to an individual filesystem) 
should go to linux-api as well as other relevant lists.

-- 
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/