Bug#971645: sshfs: truncates timestamps to whole seconds

2020-10-20 Thread Bernhard Übelacker
Am 19.10.20 um 23:43 schrieb Adam Borowski: > On Mon, Oct 19, 2020 at 10:52:45PM +0200, Bernhard Übelacker wrote: >> Dear Maintainer, >> tried to track where the time is set/retrieved for a remote file >> and came up with this location [1]. >> >> I am not sure if flag >> SSH_FILEXFER_ATTR_ACMODTIM

Bug#971645: sshfs: truncates timestamps to whole seconds

2020-10-19 Thread Bernhard Übelacker
Dear Maintainer, tried to track where the time is set/retrieved for a remote file and came up with this location [1]. I am not sure if flag SSH_FILEXFER_ATTR_ACMODTIME/SSH2_FILEXFER_ATTR_ACMODTIME is the only possible way ssh has to transfer the date, but at least that way seems to just use 32 bit

Bug#971645: sshfs: truncates timestamps to whole seconds

2020-10-19 Thread Adam Borowski
On Mon, Oct 19, 2020 at 10:52:45PM +0200, Bernhard Übelacker wrote: > Dear Maintainer, > tried to track where the time is set/retrieved for a remote file > and came up with this location [1]. > > I am not sure if flag SSH_FILEXFER_ATTR_ACMODTIME/SSH2_FILEXFER_ATTR_ACMODTIME > is the only possible

Bug#971645: sshfs: truncates timestamps to whole seconds

2020-10-03 Thread Adam Borowski
Package: sshfs Version: 3.7.0+repack-1 Severity: normal Hi! sshfs sets the sub-second part of timestamps to 0. This happens both on read (stat) and on write (utimensat). This means, the metadata of a file copied over sshfs will be different, causing unnecessary whole-file comparisons, etc. Stri