On Thu, Jun 9, 2016 at 12:08 PM, Linus Torvalds
wrote:
> On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani
> wrote:
>> CURRENT_TIME macro is not appropriate for filesystems as it
>> doesn't use the right granularity for filesystem timestamps.
On Wednesday, June 8, 2016 10:04:48 PM CEST Deepa Dinamani wrote:
>
> Signed-off-by: Deepa Dinamani
> Cc: Steve French
> Cc: linux-c...@vger.kernel.org
> Cc: samba-techni...@lists.samba.org
> Cc: Joern Engel
> Cc: Prasad Joshi
On Thu, Jun 9, 2016 at 1:38 PM, Deepa Dinamani wrote:
>
> 1. There are a few link, rename functions which assign times like this:
>
> - inode->i_ctime = dir->i_ctime = dir->i_mtime = CURRENT_TIME;
> + inode->i_ctime = dir->i_ctime = dir->i_mtime =
>
CURRENT_TIME macro is not appropriate for filesystems as it
doesn't use the right granularity for filesystem timestamps.
Use current_fs_time() instead.
CURRENT_TIME is also not y2038 safe.
This is also in preparation for the patch that transitions
vfs timestamps to use 64 bit time and hence make
On Wed, Jun 08, 2016 at 10:04:48PM -0700, Deepa Dinamani wrote:
> CURRENT_TIME macro is not appropriate for filesystems as it
> doesn't use the right granularity for filesystem timestamps.
> Use current_fs_time() instead.
>
> CURRENT_TIME is also not y2038 safe.
>
> This is also in preparation
for nilfs2 bits:
Acked-by: Ryusuke Konishi
Thanks,
Ryusuke Konishi
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals
On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani wrote:
> CURRENT_TIME macro is not appropriate for filesystems as it
> doesn't use the right granularity for filesystem timestamps.
> Use current_fs_time() instead.
Again - using the inode instead fo the syuperblock in tghis