cvs commit: src/sys/kern kern_exec.c src/sys/vm vm_map.c vm_map.h

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxxxxx>]

dillon      2004/03/12 15:09:37 PST

DragonFly src repository

  Modified files:
    sys/kern             kern_exec.c 
    sys/vm               vm_map.c vm_map.h 
  Log:
  In an rfork'd or vfork'd situation where multiple processes are sharing
  the same vmspace, and one process goes zombie, the vmspace's vm_exitingcnt
  will be non-zero.  If another process then forks or execs the exitingcnt will
  be improperly inherited by the new vmspace.  The solution is to not copy
  exitingcnt when copying to a new vmspace.
  
  Additionally, for DragonFly, I also had to fix a few cases where the upcall
  list was also being improperly inherited.
  
  Heads-up-by: Xin LI <delphij@xxxxxxxxxxxxx>
  Obtained-From: Peter Wemm <peter@xxxxxxxx> (FreeBSD-5)
  
  Revision  Changes    Path
  1.21      +6 -1      src/sys/kern/kern_exec.c
  1.23      +12 -4     src/sys/vm/vm_map.c
  1.13      +1 -0      src/sys/vm/vm_map.h


http://www.dragonflybsd.org/cvsweb/src/sys/kern/kern_exec.c.diff?r1=1.20&r2=1.21&f=h
http://www.dragonflybsd.org/cvsweb/src/sys/vm/vm_map.c.diff?r1=1.22&r2=1.23&f=h
http://www.dragonflybsd.org/cvsweb/src/sys/vm/vm_map.h.diff?r1=1.12&r2=1.13&f=h