From: Melkor Ainur <melkorainur@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: failure due to swapper and inet_sock_destruct
Date: Sat, 5 Apr 2003 22:54:19 -0800 (PST) [thread overview]
Message-ID: <20030406065419.91429.qmail@web21203.mail.yahoo.com> (raw)
Hello,
I am using the 2.4.20 kernel in a fairly high stress
bursty network environment. Every so often, I see the
following error message from the kernel:
Attempt to release TCP socket in state 10 cfbfd540
I put some tracking in the kernel, and determined that
this cfbfd540 was specifically the sk1 used in
inet_tcp_listen and looking at the sport of 0x17, it
is the telnet daemon. So it was created by xinetd for
the telnet listening socket.
The failure often happens during a period of
inactivity. The call to inet_sock_destruct happened in
the swapper context. My first question is whether
anyone has observed this behavior before. Secondly, in
order to debug the problem, I'd like to understand
what could trigger the swapper to call
inet_sock_destruct. I did further determine that the
call did not come from either tcp_close or
tcp_destroy_sock. Looking at the code, it looks like
the only call to inet_sock_destruct only happens from
sk_free. sk_free looks to be used by sock_put which
happens from sock_wfree, sklist_remove_socket, etc.
Anyway, I'll keep investigating but I could use any
help/advice on what would trigger the destruction of
an sk without a call to close the parent listening
socket. Any reason why it happened in the swapper
context?
Thanks,
Melkor
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com
next reply other threads:[~2003-04-06 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 6:54 Melkor Ainur [this message]
2003-04-07 4:49 ` James Morris
2003-04-07 15:05 ` Melkor Ainur
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=20030406065419.91429.qmail@web21203.mail.yahoo.com \
--to=melkorainur@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®