linux-kernel - Re: [PATCH][RFC][BUG] updating the ctime and mtime time stamps in msync()

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Jan 2008 22:01:09 +0100
From:	"Klaus S. Madsen" <ksm@...dk>
To:	Rik van Riel <riel@...hat.com>
Cc:	Anton Salikhmetov <salikhmetov@...il.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH][RFC][BUG] updating the ctime and mtime time stamps in msync()

On Wed, Jan 09, 2008 at 15:50:15 -0500, Rik van Riel wrote:
> > Specifically, the ctime and mtime time stamps do change
> > when modifying the mapped memory and do not change when
> > there have been no write references between the mmap()
> > and msync() system calls.
> 
> As long as the ctime and mtime stamps change when the memory is
> written to, what exactly is the problem?

A "not" is missing from the sentence above. The quote above should have
read:

> > Specifically, the ctime and mtime time stamps do _not_ change when
> > modifying the mapped memory and do not change when there have been
> > no write references between the mmap() and msync() system calls.

So essentially the problem is that mtime stamps are _never_ changed when
the file is only modified through mmap. Not even when calling msync().

-- 
Kind regards,
	Klaus S. Madsen
--
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/