linux-kernel - Daylight saving time & FAT

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-next>] [day] [month] [year] [list]

Message-ID: <a4d0c86c0911051222q1ec384a2u724e0c8b1432ddb6@mail.gmail.com>
Date:	Thu, 5 Nov 2009 21:22:45 +0100
From:	Paolo Giarrusso <p.giarrusso@...il.com>
To:	hirofumi@...l.parknet.co.jp
Cc:	linux-kernel@...r.kernel.org
Subject: Daylight saving time & FAT

Hi,
I'm an ex kernel developer, writing to you because of a problem with
FAT and its Linux driver.

When re-rsync'ing two hard drives (one VFAT, one NTFS mounted with
ntfs-3g) after a Daylight Saving Time change (I was on CEST, +0200,
now I'm on CET, +0100), I discovered a one-hour time difference over
all files (on FAT, they are one hour in future).
My current understanding is that FAT stores times relative to the
current timezone, and that's crappy (see fat_time_fat2unix(), in
fs/fat/misc.c). But with the current code, it gets even more crappy -
the same file will have a different _UTC_ timestamp depending on my
current timezone, since the current offset from UTC is added to the
stored timestamp to get the UTC time (I verified the timezone change
would perfectly explain, even in sign, the time difference I found).
That's why I guess that the FAT timestamps are wrong.
I frankly doubt that Windows is so bad.

On DOS, they could get away without any conversion at all. But on
current Windows systems? Either you find the right time zone at file
saving time (too complicated IMHO) or ignore DST when saving/restoring
time (i.e. pretend DST is not in effect, and add the shift if needed).
I don't know right now what happens.
I wrote this mail to discuss what would be the correct solution (the
second?), and if it is possible to implement it.

Thanks for your attention
Regards
-- 
Paolo Giarrusso
--
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/