Re: [issue1137] Process stuck with an empty STATE

[YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>]

On Wed, Jan 21, 2009 at 03:17:01PM +0900, YONETANI Tomokazu wrote:
> > :I played with kgdb a bit and found that these 3 processes are on zombproc
> > :but with p_stat==SACTIVE and p_lock==1.  I have no idea how it happened.
> > 
> >     This should hopefully be fixed with this commit I made in December:
> > 
> > commit 2e425d87dc98885c44799de0327ab0013a7c34d6
> > Author: Matthew Dillon <dillon@apollo.backplane.com>
> > Date:   Thu Dec 18 20:20:15 2008 -0800
> > 
> >     Close a possible bug where the p_lock for a new process inherits a
> >     non-zero value from its parent on fork(), preventing the process
> >     from being able to exit later on.
> 
> Ok, I'll try this on top of R2.0, or the pre-release of R2.2,
> depending on when the new branch becomes available.

I found a similar zombie process on a PC running -DEVELOPMENT
(as of 89f297df...), with p_stat==SACTIVE and p_lock==1.  The stuck
process was git again.  The previous ones were `git log', and this time
`git show', all of which involve $PAGER.  I tried issuing the same command
several times, but I couldn't reproduce another zombie yet.