Re: kern/45718 (processes sometimes get stuck and spin in vm_map)

[Taylor R Campbell <campbell+netbsd%mumble.net@localhost>]

The following reply was made to PR kern/45718; it has been noted by GNATS.

From: Taylor R Campbell <campbell+netbsd%mumble.net@localhost>
To: matthew green <mrg%eterna.com.au@localhost>
Cc: kern-bug-people%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
        gnats-admin%netbsd.org@localhost, rmind%NetBSD.org@localhost,
        gnats-bugs%NetBSD.org@localhost, oster%netbsd.org@localhost, 
martin%netbsd.org@localhost
Subject: Re: kern/45718 (processes sometimes get stuck and spin in vm_map)
Date: Sat, 14 Apr 2012 19:23:58 +0000

    Date: Sun, 15 Apr 2012 05:14:06 +1000
    From: matthew green <mrg%eterna.com.au@localhost>
 
    this looks like the execargs pool leak that greg oster has a patch for.
    (reproduced below.)
 
    @@ -1991,6 +1991,8 @@ spawn_return(void *arg)
                    rw_exit(&exec_lock);
            }
 
    +   execve_free_data(&spawn_data->sed_exec);
 
 Isn't that code path reachable only if someone uses posix_spawn?
 Certainly nothing in a 5.1 userland will use posix_spawn, and although
 I suppose my having run the 6.99.4 tests in a chroot might have
 triggered it, it wouldn't explain the earlier problem I reported,
 because I believe I reported that before posix_spawn was imported.