From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: kuznet@ms2.inr.ac.ru, vgusev@openvz.org, mcmanus@ducksong.com,
xemul@openvz.org, netdev@vger.kernel.org,
ilpo.jarvinen@helsinki.fi, linux-kernel@vger.kernel.org
Subject: Re: [TCP]: TCP_DEFER_ACCEPT causes leak sockets
Date: Tue, 17 Jun 2008 00:38:32 -0700 (PDT) [thread overview]
Message-ID: <20080617.003832.130616157.davem@davemloft.net> (raw)
In-Reply-To: <20080617072658.GA12535@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Tue, 17 Jun 2008 09:26:58 +0200
> So since there's no clear bug pattern and no sure reproducability on my
> side i'd suggest we track this problem separately and "do nothing" right
> now. I've excluded this warning from my 'is the freshly booted kernel
> buggy' list of conditions of -tip testing so it's not holding me up.
I'm going to push the revert through just to be safe and I think it's
a good idea to do so because all of those defer accept changes should
be resubmitted as a group for 2.6.27
> and i can apply any test-patch if that would be helpful - if it does a
> WARN_ON() i'll notice it. (pure extra debug printks with no stack trace
> are much harder to notice in automated tests)
I don't have time to work on your bug, sorry. Someone else will
have to step forward and help you with it.
FWIW I don't think your TX timeout problem has anything to do with
packet ordering. The TX element of the network device is totally
stateless, but it's hanging under some set of circumstances to the
point where we timeout and reset the hardware to get it going again.
next prev parent reply other threads:[~2008-06-17 7:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 12:58 [TCP]: TCP_DEFER_ACCEPT causes leak sockets Vitaliy Gusev
2008-06-11 13:57 ` Alexey Kuznetsov
2008-06-11 23:52 ` David Miller
2008-06-12 23:32 ` David Miller
2008-06-13 6:30 ` Ingo Molnar
2008-06-13 9:32 ` David Miller
2008-06-13 11:09 ` Ingo Molnar
2008-06-13 11:47 ` Ingo Molnar
2008-06-13 21:10 ` Ingo Molnar
2008-06-16 23:59 ` David Miller
2008-06-17 7:26 ` Ingo Molnar
2008-06-17 7:38 ` David Miller [this message]
2008-06-17 8:09 ` Ingo Molnar
2008-06-17 8:09 ` Ingo Molnar
2008-06-17 8:32 ` Ingo Molnar
2008-06-17 8:32 ` Ingo Molnar
2008-06-17 9:08 ` David Miller
2008-06-17 9:27 ` Ingo Molnar
2008-06-17 9:27 ` Ingo Molnar
2008-06-17 9:29 ` David Miller
2008-06-17 9:39 ` Ingo Molnar
2008-06-17 9:39 ` Ingo Molnar
2008-06-18 18:50 ` [E1000-devel] " Kok, Auke
2008-06-18 20:08 ` Ingo Molnar
2008-06-18 20:08 ` Ingo Molnar
2008-06-18 21:25 ` [E1000-devel] " Kok, Auke
2008-06-18 22:12 ` David Miller
2008-06-18 22:12 ` David Miller
2008-06-19 7:06 ` Jarek Poplawski
2008-06-19 7:06 ` Jarek Poplawski
2008-06-18 21:32 ` [E1000-devel] " Ingo Molnar
2008-06-18 21:32 ` Ingo Molnar
2008-06-18 21:41 ` [E1000-devel] " Denys Fedoryshchenko
2008-06-18 21:41 ` Denys Fedoryshchenko
2008-06-18 22:05 ` [E1000-devel] " Ingo Molnar
2008-06-18 22:05 ` Ingo Molnar
2008-06-18 22:44 ` [E1000-devel] " Denys Fedoryshchenko
2008-06-18 22:44 ` Denys Fedoryshchenko
2008-06-18 23:14 ` [E1000-devel] " Ingo Molnar
2008-06-18 23:14 ` Ingo Molnar
2008-06-17 8:43 ` Vitaliy Gusev
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=20080617.003832.130616157.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mcmanus@ducksong.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=vgusev@openvz.org \
--cc=xemul@openvz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.