From: Dave McCracken <dmccr@us.ibm.com>
To: Linux Memory Management <linux-mm@kvack.org>
Subject: Re: Question about locking in mmap.c
Date: Wed, 28 May 2003 17:10:06 -0500 [thread overview]
Message-ID: <133810000.1054159806@baldur.austin.ibm.com> (raw)
In-Reply-To: <33460000.1054135672@baldur.austin.ibm.com>
--On Wednesday, May 28, 2003 10:27:52 -0500 Dave McCracken
<dmccr@us.ibm.com> wrote:
> My question is what is page_table_lock supposed to be protecting against?
> Am I wrong that mmap_sem is sufficient to protect against concurrent
> changes to the vmas?
I decided one way to find out was to remove the page_table_lock from mmap.
I discovered one place it protects against is vmtruncate(), so it's
definitely needed as it stands. I got an oops in zap_page_range() called
from vmtruncate().
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-28 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 15:27 Dave McCracken
2003-05-28 16:28 ` Hugh Dickins
2003-05-28 22:10 ` Dave McCracken [this message]
2003-05-29 2:10 ` William Lee Irwin III
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=133810000.1054159806@baldur.austin.ibm.com \
--to=dmccr@us.ibm.com \
--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