linux-mips
[Top] [All Lists]

Re: what is this?

To: mjhsieh@helix.life.nthu.edu.tw (Francis M. J. Hsieh)
Subject: Re: what is this?
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
Date: Sat, 1 Aug 1998 14:02:26 +0100 (BST)
Cc: linux@cthulhu.engr.sgi.com
In-reply-to: <19980801140032.A1004@helix.life.nthu.edu.tw> from "Francis M. J. Hsieh" at Aug 1, 98 02:00:32 pm
Sender: owner-linux@cthulhu.engr.sgi.com
> okay, I am reporting again.
> 
> I happened to meet this before, maybe it is a rare case.
>   Socket destroy delayed (r=0 w=112)
>   Socket destroy delayed (r=0 w=256)
> 
> Any idea? Had anyone seen that before?

When a socket has buffers charged to it the socket cant be destroyed so
the kernel hangs on to it. It indicates one of several things - a socket
that has some state timeouts left to do that are longer than 10 secs 
after the close, a socket that has buffers queued up with a very constipated
driver, or a leak.

Alan


<Prev in Thread] Current Thread [Next in Thread>