linux-kernel - Re: [patch] x86-64 ext2/ext3 datestamp problem

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: <45C8FC01.8060506@zytor.com>
Date:	Tue, 06 Feb 2007 14:06:57 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Markus Rechberger <markus.rechberger@....com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [patch] x86-64 ext2/ext3 datestamp problem

Markus Rechberger wrote:
> H. Peter Anvin wrote:
>> Markus Rechberger wrote:
>>> My debian system's coreutils package only allows dates between 1902 and
>>> 2038, but it might be interesting to get that right if it's wrong.
>>>
>>> touch (GNU coreutils) 5.97 just says invalid dateformat to 2050-01-01
>> Lemme guess, you're on a 32-bit system...
>>
> 
> I have both here, 64 and 32bit
> If I touch a file with 1905 on my 32bit system and remount the disk the
> date will remain at 1905 without any patch.
> 

The reason is that most 32-bit systems (e.g. i386) only have a 32-bit 
time_t, so the user space interface wraps around in 2038.

However, most 64-bit systems (e.g. x86_64) have 64-bit time_t, and thus 
don't have that problem.

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