This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: how do exit and _exit affect mmapped memory?

From: Dmitry Goncharov <dgoncharov at users dot sf dot net>
To: libc-help at sourceware dot org
Cc: keisial at gmail dot com, godmar at gmail dot com
Date: Sun, 9 Sep 2012 18:04:23 -0400
Subject: Re: how do exit and _exit affect mmapped memory?
References: <20120909031203.GC10479@madrid><CAB4+JYKgnhpsYB=hnZ_APzJoPg6ppEQt+Cbgd2vW2iD3A1CEYg@mail.gmail.com><504CB4B1.3060701@gmail.com>

On Sun, Sep 09, 2012 at 05:24:33PM +0200, Ángel González wrote:
> On 09/09/12 06:32, Godmar Back wrote:
> > It'll be saved in all cases, no matter what the process does or how it exits.
> >
> >  - Godmar
> Assuming the OS doesn't crash after that before it updates the file on
> disk :)
> 
> Which is highly unlikely, if you need to protect against that
> eventuality, call msync()
> 
Thanks, folks.
Do you, by any chance, know where in the source tree the code which flushes
these pages can be found?

regards, Dmitry

Follow-Ups:
- Re: how do exit and _exit affect mmapped memory?
  - From: Godmar Back

References:
- how do exit and _exit affect mmapped memory?
  - From: Dmitry Goncharov
- Re: how do exit and _exit affect mmapped memory?
  - From: Godmar Back
- Re: how do exit and _exit affect mmapped memory?
  - From: Ángel González

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]