netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: "David S. Miller" <davem@redhat.com>, netdev@oss.sgi.com
Subject: Re: Dump of TCP hang in established state
Date: Thu, 29 May 2003 14:50:08 -0700	[thread overview]
Message-ID: <3ED68090.5040903@us.ibm.com> (raw)
In-Reply-To: <1054238230.709.1.camel@tux.rsn.bth.se>

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? And should potentially
fix such issues or other seeming weirdnesses that might be
happening in both sendmsg() and sendfile() code paths? Any other
symptoms or particulars? I'm wondering if this addresses
might explain some other bugs we have run into (not
identified as TCP yet)?


thanks,
Nivedita

  reply	other threads:[~2003-05-29 21:50 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 [this message]
2003-05-29 21:52         ` David S. Miller
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=3ED68090.5040903@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=davem@redhat.com \
    --cc=gandalf@wlug.westbo.se \
    --cc=netdev@oss.sgi.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).