From: "David S. Miller" <davem@redhat.com>
To: niv@us.ibm.com
Cc: gandalf@wlug.westbo.se, netdev@oss.sgi.com
Subject: Re: Dump of TCP hang in established state
Date: Thu, 29 May 2003 14:52:46 -0700 (PDT) [thread overview]
Message-ID: <20030529.145246.23019115.davem@redhat.com> (raw)
In-Reply-To: <3ED68090.5040903@us.ibm.com>
From: Nivedita Singhvi <niv@us.ibm.com>
Date: Thu, 29 May 2003 14:50:08 -0700
Martin Josefsson wrote:
> I've just tested 2.5-bk and I can still reproduce it.
> The wording of my mail might have been a bit wrong, I don't see complete
> hangs, just ~2 minute stalls in ESTABLISHED state and then it continues
> like nothing happened.
>
This actually addresses a situation of memory corruption
and illegal reference panics, correct?
It prevents TCP input from "reading" bogus memory when comparing
time_wait buckets to the saddr/sport/daddr/dport of an incoming
packet.
By bogus memory I mean it's some large offset from the base of the
struct tcp_tw_bucket structure, past it's end.
next prev parent reply other threads:[~2003-05-29 21:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 15:51 Dump of TCP hang in established state Martin Josefsson
2003-05-14 9:08 ` James Morris
2003-05-21 17:19 ` Nivedita Singhvi
2003-05-21 19:31 ` Martin Josefsson
2003-05-21 18:58 ` Nivedita Singhvi
2003-05-21 19:54 ` Martin Josefsson
2003-05-21 19:59 ` Nivedita Singhvi
2003-05-21 19:39 ` Martin Josefsson
2003-05-21 23:10 ` David S. Miller
2003-05-22 0:35 ` Nivedita Singhvi
2003-05-29 9:41 ` David S. Miller
2003-05-29 14:03 ` Martin Josefsson
2003-05-29 19:57 ` Martin Josefsson
2003-05-29 21:50 ` Nivedita Singhvi
2003-05-29 21:52 ` David S. Miller [this message]
2003-05-29 21:54 ` David S. Miller
2003-05-29 22:00 ` Martin Josefsson
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=20030529.145246.23019115.davem@redhat.com \
--to=davem@redhat.com \
--cc=gandalf@wlug.westbo.se \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
/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).