why current->mm in mm/mmap.c's dup_mmap?

why current->mm in mm/mmap.c's dup_mmap?

[Ed L Cashin]

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>