From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Olaf Kirch <okir@lst.de>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: very strange inet_sock corruption with rpc
Date: Thu, 26 Apr 2007 09:00:27 -0400 [thread overview]
Message-ID: <4630A26B.2050406@hp.com> (raw)
In-Reply-To: <200704260849.41485.okir@lst.de>
Olaf Kirch wrote:
> On Wednesday 25 April 2007 23:03, Vlad Yasevich wrote:
>> It looks like someone is stepping all over the inet_sock.
>> We'll continue looking, but if anyone has any ideas of what might
>> be going on, I'd appreciate it.
>
> This could be a socket in TIME_WAIT. A socket entering
> TIME_WAIT will be replaced by an inet_timewait_sock, which is
> a kind of truncated inet_sock.
>
> Olaf
Olaf
Thank you. I think this is what we are seeing.
-vlad
next prev parent reply other threads:[~2007-04-26 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 21:03 very strange inet_sock corruption with rpc Vlad Yasevich
2007-04-25 22:13 ` Sridhar Samudrala
2007-04-26 12:52 ` Vlad Yasevich
2007-04-26 6:49 ` Olaf Kirch
2007-04-26 13:00 ` Vlad Yasevich [this message]
2007-04-26 13:00 ` Arnaldo Carvalho de Melo
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=4630A26B.2050406@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=netdev@vger.kernel.org \
--cc=okir@lst.de \
/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;
as well as URLs for NNTP newsgroup(s).