All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Lehmann <linux-kernel@plan9.de>
To: linux-kernel@vger.kernel.org
Subject: sockets stuck in FIN_WAIT2 and CLOSE_WAIT state in 2.6.10
Date: Mon, 10 Jan 2005 03:11:09 +0100	[thread overview]
Message-ID: <20050110021108.GA9758@schmorp.de> (raw)

After upgrading to linux-2.6.10 (on 2004-12-26), my rsh processes start to
hang despite the server side having closed the connection.

Inspection showed that one of the two rsh processes exited:

   16011 ?        SN     0:00      0     6  1717   600  0.0 rsh ruth cd xmltv && ./upd
   16012 ?        ZN     0:00      0     0     0     0  0.0 [rsh] <defunct>

lsof shows both sockets:

   rsh     16011 root    3u  IPv4 6454542          TCP doom:1014->ruth:shell (FIN_WAIT2)
   rsh     16011 root    5u  IPv4 6454545          TCP doom:1013->ruth:1023 (CLOSE_WAIT)

and the remaining rsh process hangs in select on the FIN_WAIT2 socket:

   select(6, [3], NULL, NULL, NULL

Some of the hung processes are stuck for 14 days now.

I did not have the same problem with 2.6.10-rc1, or 2.6.8.1, which I used
before.

This is on a x86 SMP kernel using Debian GNU/Linux. If this problem is
already known, my apologies, I couldn't access a kernel list archive. If
you want more info, feel free to contact me.

-- 
                The choice of a
      -----==-     _GNU_
      ----==-- _       generation     Marc Lehmann
      ---==---(_)__  __ ____  __      pcg@goof.com
      --==---/ / _ \/ // /\ \/ /      http://schmorp.de/
      -=====/_/_//_/\_,_/ /_/\_\      XX11-RIPE

                 reply	other threads:[~2005-01-10  2:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050110021108.GA9758@schmorp.de \
    --to=linux-kernel@plan9.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.