From: Eric Dumazet <eric.dumazet@gmail.com>
To: dormando <dormando@rydia.net>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: BUG: IPv4: Attempt to release TCP socket in state 1
Date: Tue, 05 Mar 2013 06:46:35 -0800 [thread overview]
Message-ID: <1362494795.15793.113.camel@edumazet-glaptop> (raw)
In-Reply-To: <alpine.DEB.2.02.1303042138330.7811@localhost6.localdomain6>
On Mon, 2013-03-04 at 21:44 -0800, dormando wrote:
> No 3rd party modules. There's a tiny patch for controlling initcwnd from
> userspace and another one for the extra_free_kbytes tunable that I brought
> up in another thread. We've had the initcwnd patch in for a long time
> without trouble. The extra_free_kbytes tunable isn't even being used yet,
> so all that's doing is adding a 0 somewhere.
>
> Only two iptables rules loaded: global NOTRACK rules for PREROUTING/OUTPUT
> in raw.
>
> Kernel's as close to pristine as I can make it. We had the 10g patch in
> but I've dropped it.
> --
Hmm, I spent time on this bug report but found nothing.
Please post as much information as you can on your setup.
I see you use macvlan, bridge, so maybe there is a configuration issue
(and a kernel bug of course)
next prev parent reply other threads:[~2013-03-05 14:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1303041547080.7811@localhost6.localdomain6>
2013-03-05 3:47 ` BUG: IPv4: Attempt to release TCP socket in state 1 Cong Wang
2013-03-05 5:07 ` Eric Dumazet
2013-03-05 5:44 ` dormando
2013-03-05 14:46 ` Eric Dumazet [this message]
2013-03-07 0:41 ` dormando
2013-03-07 13:46 ` Eric Dumazet
2013-03-08 7:09 ` dormando
2013-03-14 21:21 ` dormando
2013-03-14 22:56 ` Eric Dumazet
2013-03-14 23:15 ` dormando
2013-03-14 23:19 ` Eric Dumazet
2013-03-16 17:36 ` Eric Dumazet
2013-03-16 17:44 ` Eric Dumazet
2013-03-16 20:16 ` dormando
2013-03-17 9:21 ` dormando
2013-03-17 16:33 ` Eric Dumazet
2013-03-17 16:52 ` Eric Dumazet
2013-03-17 19:00 ` Eric Dumazet
2013-03-17 6:39 ` Hannes Frederic Sowa
2013-03-17 7:53 ` Hannes Frederic Sowa
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=1362494795.15793.113.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=dormando@rydia.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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