linux-kernel - Wrong atime on recent kernels

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]

Date:	Mon, 14 Dec 2009 22:17:50 +0100
From:	Petr Titěra <petr@...era.eu>
To:	linux-kernel@...r.kernel.org
Subject: Wrong atime on recent kernels

Hello,

       I see some strange file modification times recently. It seems to 
me that in some situations, kernel allows to set nanoseconds part of  
file access, modification or change time  to 100000000 ns. Problem seems 
to be in some generic part of kernel because I see it on several 
different filesysytems (ext4 and nilf2). These is I've got during my 
testing on kernel  2.6.32-tip-08309-gad8e75a.

  File: `./Documentation/dvb/contributors.txt'
  Size: 3035            Blocks: 8          IO Block: 4096   regular file
Device: fe04h/65028d    Inode: 818         Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2009-12-14 10:29:04.1000000000 +0100
Modify: 2009-12-14 10:29:04.1000000000 +0100
Change: 2009-12-14 10:29:04.1000000000 +0100

See that all times of that file ends with 1e6 nanoseconds.

Petr Titera
--
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/