From: Clemens Kolbitsch <clemens.kol@gmx.at>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: Forbid deletion of memory mappings
Date: Tue, 4 Sep 2007 12:29:55 +0200 [thread overview]
Message-ID: <200709041229.55610.clemens.kol@gmx.at> (raw)
In-Reply-To: <46DD30CC.4060907@aitel.hist.no>
> If you are doing research, consider these methods:
> 1. Change vma_merge() so it always fail to merge mappings
>
> or
>
> 2. Set up your "mappings duplicated in userspace" so
> they too merge in the same way.
>
> Helge Hafting
Hi!
Thanks for your answer, however you (too) misunderstood: Merging of the vma's
is not the problem and I understand why the kernel does so.
The real problem is that it deletes mappings it should not be deleting... in
my case, I've found out that a possible reason for the deletions is that the
stack tries to grow or other large areas of memory are allocated and my
mapping is taking up the memory that the kernel wants to reserve.
However, this has been dealt with in some other reply - I decided to simply
relocate my mappings to another memory area as soon as the kernel tries to
delete them.
This is not really all that efficient, but it does not matter right now in my
case.
Thanks again for your answer - I appreciate it!
next prev parent reply other threads:[~2007-09-04 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 16:44 Clemens Kolbitsch
2007-08-30 17:07 ` Jiri Kosina
2007-08-30 17:09 ` Clemens Kolbitsch
2007-08-30 21:32 ` Clemens Kolbitsch
2007-08-30 21:34 ` Jiri Kosina
2007-08-30 21:41 ` Clemens Kolbitsch
2007-08-30 21:50 ` Valdis.Kletnieks
2007-08-30 22:05 ` Clemens Kolbitsch
2007-09-04 10:17 ` Helge Hafting
2007-09-04 10:29 ` Clemens Kolbitsch [this message]
2007-09-04 14:53 ` linux-os (Dick Johnson)
2007-08-30 21:55 ` Jiri Kosina
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=200709041229.55610.clemens.kol@gmx.at \
--to=clemens.kol@gmx.at \
--cc=Valdis.Kletnieks@vt.edu \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®