From: "Chris Friesen" <cfriesen@nortel.com>
To: Rik van Riel <riel@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Eugene V. Lyubimkin" <jackyf.devel@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
hugh <hugh@veritas.com>
Subject: Re: mmap: is default non-populating behavior stable?
Date: Tue, 04 Nov 2008 09:56:37 -0600 [thread overview]
Message-ID: <491070B5.2060209@nortel.com> (raw)
In-Reply-To: <490F8005.9020708@redhat.com>
Rik van Riel wrote:
> Peter Zijlstra wrote:
>> The exact interaction of mmap() and truncate() I'm not exactly clear on.
>
> Truncate will reduce the size of the mmaps on the file to
> match the new file size, so processes accessing beyond the
> end of file will get a segmentation fault (SIGSEGV).
I suspect Peter was talking about using truncate() to set the initial
file size, effectively increasing rather than reducing it.
Chris
WARNING: multiple messages have this Message-ID (diff)
From: "Chris Friesen" <cfriesen@nortel.com>
To: Rik van Riel <riel@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Eugene V. Lyubimkin" <jackyf.devel@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
hugh <hugh@veritas.com>
Subject: Re: mmap: is default non-populating behavior stable?
Date: Tue, 04 Nov 2008 09:56:37 -0600 [thread overview]
Message-ID: <491070B5.2060209@nortel.com> (raw)
In-Reply-To: <490F8005.9020708@redhat.com>
Rik van Riel wrote:
> Peter Zijlstra wrote:
>> The exact interaction of mmap() and truncate() I'm not exactly clear on.
>
> Truncate will reduce the size of the mmaps on the file to
> match the new file size, so processes accessing beyond the
> end of file will get a segmentation fault (SIGSEGV).
I suspect Peter was talking about using truncate() to set the initial
file size, effectively increasing rather than reducing it.
Chris
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-11-04 15:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 21:57 mmap: is default non-populating behavior stable? Eugene V. Lyubimkin
2008-11-03 22:41 ` Peter Zijlstra
2008-11-03 22:41 ` Peter Zijlstra
2008-11-03 22:49 ` Rik van Riel
2008-11-03 22:49 ` Rik van Riel
2008-11-04 15:56 ` Chris Friesen [this message]
2008-11-04 15:56 ` Chris Friesen
2008-11-04 16:07 ` Peter Zijlstra
2008-11-04 16:07 ` Peter Zijlstra
2008-11-04 16:28 ` Alan Cox
2008-11-04 16:28 ` Alan Cox
2008-11-04 16:51 ` Eugene V. Lyubimkin
2008-11-05 16:42 ` Hugh Dickins
2008-11-05 16:42 ` Hugh Dickins
2008-11-05 16:54 ` Alan Cox
2008-11-05 16:54 ` Alan Cox
2008-11-05 17:50 ` Eugene V. Lyubimkin
2008-11-05 23:31 ` Hugh Dickins
2008-11-05 23:31 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491070B5.2060209@nortel.com \
--to=cfriesen@nortel.com \
--cc=hugh@veritas.com \
--cc=jackyf.devel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.