On Thu, 2007-02-22 at 21:48 +0100, Miklos Szeredi wrote: > > This still does not address the situation where a file is 'permanently' > > mmap'd, does it? > > So? If application doesn't do msync, then the file times won't be > updated. That's allowed by the standard, and so portable applications > will have to call msync. It is allowed, but it is clearly not useful behaviour. Nowhere is it set in stone that we should be implementing just the minimum allowed. Trond - 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] update ctime and mtime for mmaped write
- From: Miklos Szeredi <[email protected]>
- Re: [PATCH] update ctime and mtime for mmaped write
- References:
- [PATCH] update ctime and mtime for mmaped write
- From: Miklos Szeredi <[email protected]>
- Re: [PATCH] update ctime and mtime for mmaped write
- From: Andrew Morton <[email protected]>
- Re: [PATCH] update ctime and mtime for mmaped write
- From: Miklos Szeredi <[email protected]>
- Re: [PATCH] update ctime and mtime for mmaped write
- From: Peter Staubach <[email protected]>
- Re: [PATCH] update ctime and mtime for mmaped write
- From: Miklos Szeredi <[email protected]>
- Re: [PATCH] update ctime and mtime for mmaped write
- From: Peter Staubach <[email protected]>
- Re: [PATCH] update ctime and mtime for mmaped write
- From: Miklos Szeredi <[email protected]>
- [PATCH] update ctime and mtime for mmaped write
- Prev by Date: Re: [RFC][PATCH -mm] mmc build fix
- Next by Date: Re: NO_HZ: timer interrupt stuck [Re: Linux 2.6.21-rc1]
- Previous by thread: Re: [PATCH] update ctime and mtime for mmaped write
- Next by thread: Re: [PATCH] update ctime and mtime for mmaped write
- Index(es):
 |