From: David Miller <davem@davemloft.net>
To: khorenko@openvz.org
Cc: netdev@vger.kernel.org
Subject: Re: tcp: sending reset to the already closed socket
Date: Thu, 24 Jun 2010 21:56:33 -0700 (PDT) [thread overview]
Message-ID: <20100624.215633.233693894.davem@davemloft.net> (raw)
In-Reply-To: <4C1A2502.1030502@openvz.org>
Your email was a better commit message (lots of useful traces and
information and analysis, that will be useful to someone in the future
looking at this commit) than your patch's actual commit message which
was terse and non-descriptive. :-)
So I combined the two :-)
I've applied this to net-next-2.6, if this problem causes serious
documentable grief for a significant number of real users we can
toss it into net-2.6 or -stable later.
Thanks!
prev parent reply other threads:[~2010-06-25 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:37 tcp: sending reset to the already closed socket Konstantin Khorenko
2010-06-25 4:56 ` David Miller [this message]
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=20100624.215633.233693894.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=khorenko@openvz.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).