mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Clemens Kolbitsch <clemens.kol@gmx.at>
To: linux-kernel@vger.kernel.org
Cc: Jiri Kosina <jikos@jikos.cz>
Subject: Re: Forbid deletion of memory mappings
Date: Thu, 30 Aug 2007 23:32:42 +0200	[thread overview]
Message-ID: <200708302332.42744.clemens.kol@gmx.at> (raw)
In-Reply-To: <Pine.LNX.4.64.0708301906020.2460@twin.jikos.cz>

On Thursday 30 August 2007 19:07:05 you wrote:
> On Thu, 30 Aug 2007, Clemens Kolbitsch wrote:
> > It all works perfectly well (creating & deleting the additional
> > mappings), however, when the kernel feels like it needs to allocate a
> > mapping in user-space it sometimes deletes my mapping and overwrites it
> > with the new one, although there is plenty of free memory at some other
> > location.
>
> Hi Clemens,
>
> what do you mean by "overwrites it"? It just probably merges your vma with
> the newly created one, right?

does really noone have an answer for me?? i'm having the hardest time to find 
a work-around for it.

is there no way to tell the kernel, that a certain mapping must not be 
removed, no matter what (except of course an explicit call to sys_unmap, of 
course)?

  parent reply	other threads:[~2007-08-30 21:33 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 [this message]
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
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=200708302332.42744.clemens.kol@gmx.at \
    --to=clemens.kol@gmx.at \
    --cc=jikos@jikos.cz \
    --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®