Date: Sun, 29 Apr 2018 03:37:54 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Message-ID: <bug-217560-3630-tbNHwew00E@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217560-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-217560-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 --- Comment #5 from Damjan Jovanovic <damjan.jov@gmail.com> --- Created attachment 192889 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D192889&action= =3Dedit Use vfs_timestamp() instead of getnanotime() in msdosfs I've noticed msdosfs uses getnanotime() to generate timestamps, unlike ufs, ext2fs, devfs, nandfs, nfsclient, nfsserver, and tmpfs, which all use the better vfs_timestamp() function instead (which allows filesystem timestamp granularity to be configured using the vfs.timestamp_precision sysctl). Only autofs and msdosfs use getnanotime(). Patching msdosfs to use vfs_timestamp() instead, seems to also fix this bug here, with msdosfs timestamps having the timezone offset added to them a se= cond time when read. Please find my patch attached. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217560-3630-tbNHwew00E>