From: Ed L Cashin <ecashin@uga.edu>
To: linux-mm@kvack.org
Subject: why current->mm in mm/mmap.c's dup_mmap?
Date: Thu, 19 Jun 2003 13:47:31 -0400 [thread overview]
Message-ID: <20030619134731.A25935@atlas.cs.uga.edu> (raw)
Hi. In mm/mmap.c there's a static inline function,
dup_mmap, that only has one caller, namely copy_mm.
copy_mm provides dup_mmap with an oldmm parameter
with a value from current->mm.
I'd expect dup_mmap to use that parameter instead
of ever using current->mm, but instead, dup_mmap
does semaphore down and up on oldmm but otherwise
uses current->mm.
Why does dup_mmap use current->mm at all?
--
--Ed L Cashin | PGP public key:
ecashin@uga.edu | http://noserose.net/e/pgp/
--
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>
reply other threads:[~2003-06-19 17:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030619134731.A25935@atlas.cs.uga.edu \
--to=ecashin@uga.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