linux-kernel - Re: BUG: IPv4: Attempt to release TCP socket in state 1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1362494795.15793.113.camel@edumazet-glaptop>
Date:	Tue, 05 Mar 2013 06:46:35 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	dormando <dormando@...ia.net>
Cc:	Cong Wang <xiyou.wangcong@...il.com>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: BUG: IPv4: Attempt to release TCP socket in state 1

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)




--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/