Re: [PATCH] tmpfs time granularity fix for [acm]time moving backwards.

>
>Test output from a filesystem supporting sub-second timestamps (jfs,xfs,ramfs):
>creat:   m=1149891452.928796249 c=1149891452.928796249 a=1149891452.928796249
>futimes: m=1149891452.928796249 c=1149891452.928796249 a=1149891452.928796249
>
>Test output from the tmpfs filesystem with the patch below:
>creat:   m=1149892086.382150894 c=1149892086.382150894 a=1149892075.473249075
>futimes: m=1149892086.383150885 c=1149892086.383150885 a=1149892086.383150885
>
Is it normal that creat and futimes match for jfs/xfs?


>Signed-off-by: Robin H. Johnson <[email protected]>
>
Hint: Cc it to the shmem.c maintainer, or it may get missed :)



Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] tmpfs time granularity fix for [acm]time moving backwards.
  - From: "Robin H. Johnson" <[email protected]>

References:
- [PATCH] tmpfs time granularity fix for [acm]time moving backwards.
  - From: "Robin H. Johnson" <[email protected]>

Prev by Date: Re: CSCAN vs CFQ I/O scheduler benchmark results
Next by Date: Re: [PATCH]: Adding a counter in vma to indicate the number of physical pages backing it
Previous by thread: [PATCH] tmpfs time granularity fix for [acm]time moving backwards.
Next by thread: Re: [PATCH] tmpfs time granularity fix for [acm]time moving backwards.
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]