linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: [RFT] [PATCH] kanoj-mm1-2.2.5 ia32 big memory patch
Date: Tue, 11 May 1999 01:16:08 +0100 (BST)	[thread overview]
Message-ID: <14135.30408.623997.961605@dukat.scot.redhat.com> (raw)
In-Reply-To: <199905110010.RAA45630@google.engr.sgi.com>

Hi,

On Mon, 10 May 1999 17:10:14 -0700 (PDT), kanoj@google.engr.sgi.com
(Kanoj Sarcar) said:

> Btw, is mmap_sem really needed for find_extend_vma, since we are already
> holding lock_kernel (which mmap/munmap also gets)?

Yes: find_extend_vma modifies the vma, so you have to make sure that you
aren't doing this while somebody else already has the mm semaphore.  You
don't want to modify the vma while another process is doing the page
fault, so you still need to serialise.

The mmap code allocates new vmas, which calls kmalloc, and that can
block if you run out of memory.  It really isn't safe to extend the vma
while another thread is blocked like that.

--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  reply	other threads:[~1999-05-11  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-10 17:33 Kanoj Sarcar
1999-05-10 23:41 ` Stephen C. Tweedie
1999-05-11  0:10   ` Kanoj Sarcar
1999-05-11  0:16     ` Stephen C. Tweedie [this message]
1999-05-12  3:19       ` Kanoj Sarcar

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=14135.30408.623997.961605@dukat.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=kanoj@google.engr.sgi.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.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