This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> The Linux code modifies atime when it's mapped. And it doesn't update atime on read faults as well? That is permissible behavior, but not very helpful. It makes atime pretty useless if it's possible there are mmap readers. There could be a process that opened the file and mmap'd it a year ago, and then later something does a write so mtime > atime; then if the first process reads the new data, atime remains unchanged and sometime contemplating mtime vs atime would conclude that the new data has not been read by anyone.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |