From: dormando <dormando@rydia.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
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: Thu, 14 Mar 2013 16:15:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1303141610490.16308@dflat> (raw)
In-Reply-To: <1363301786.29475.40.camel@edumazet-glaptop>
> On Thu, 2013-03-14 at 14:21 -0700, dormando wrote:
> > >
> > > diff --git a/net/ipv4/af_inet.c b/net/ipv4/af_inet.c
> > > index 68f6a94..1d4d97e 100644
> > > --- a/net/ipv4/af_inet.c
> > > +++ b/net/ipv4/af_inet.c
> > > @@ -141,8 +141,9 @@ void inet_sock_destruct(struct sock *sk)
> > > sk_mem_reclaim(sk);
> > >
> > > if (sk->sk_type == SOCK_STREAM && sk->sk_state != TCP_CLOSE) {
> > > - pr_err("Attempt to release TCP socket in state %d %p\n",
> > > - sk->sk_state, sk);
> > > + pr_err("Attempt to release TCP socket family %d in state %d %p\n",
> > > + sk->sk_family, sk->sk_state, sk);
> > > + WARN_ON_ONCE(1);
> > > return;
> > > }
> > > if (!sock_flag(sk, SOCK_DEAD)) {
> >
> > [58377.436522] IPv4: Attempt to release TCP socket family 2 in state 1
> > ffff8813fbad9500
>
> There is no stack information on the WARN_ON_ONCE(1) ?
*sigh*. it's been a long month, sorry:
[58377.436522] IPv4: Attempt to release TCP socket family 2 in state 1
ffff8813fbad9500
[58377.436539] ------------[ cut here ]------------
[58377.436545] WARNING: at net/ipv4/af_inet.c:146
inet_sock_destruct+0x176/0x200()
[58377.436546] Hardware name: X9DR3-F
[58377.436547] Modules linked in: bridge coretemp ghash_clmulni_intel
ipmi_watchdog ipmi_devintf gpio_ich microcode ixgbe sb_edac edac_core mei
lpc_ich mfd_core mdio ipmi_si ipmi_msghandler iptable_nat nf_nat_ipv4
nf_nat isci libsas igb ptp pps_core
[58377.436563] Pid: 0, comm: swapper/0 Not tainted 3.8.2 #3
[58377.436564] Call Trace:
[58377.436566] <IRQ> [<ffffffff8104964f>] warn_slowpath_common+0x7f/0xc0
[58377.436572] [<ffffffff810496aa>] warn_slowpath_null+0x1a/0x20
[58377.436574] [<ffffffff816032e6>] inet_sock_destruct+0x176/0x200
[58377.436578] [<ffffffff815ec8e0>] ? tcp_write_timer_handler+0x1b0/0x1b0
[58377.436581] [<ffffffff8156ee8d>] __sk_free+0x1d/0x140
[58377.436583] [<ffffffff815ec8e0>] ? tcp_write_timer_handler+0x1b0/0x1b0
[58377.436585] [<ffffffff8156efd5>] sk_free+0x25/0x30
[58377.436586] [<ffffffff815ec929>] tcp_write_timer+0x49/0x70
[58377.436590] [<ffffffff81059259>] call_timer_fn+0x49/0x130
[58377.436593] [<ffffffff8107a07f>] ? scheduler_tick+0x15f/0x190
[58377.436596] [<ffffffff81059854>] run_timer_softirq+0x224/0x290
[58377.436598] [<ffffffff81058f76>] ? update_process_times+0x76/0x90
[58377.436600] [<ffffffff815ec8e0>] ? tcp_write_timer_handler+0x1b0/0x1b0
[58377.436602] [<ffffffff8108ebd4>] ? ktime_get+0x54/0xe0
[58377.436604] [<ffffffff810518a7>] __do_softirq+0xc7/0x230
[58377.436608] [<ffffffff8168fd4c>] call_softirq+0x1c/0x30
[58377.436611] [<ffffffff81004415>] do_softirq+0x55/0x90
[58377.436613] [<ffffffff810516a5>] irq_exit+0x85/0xa0
[58377.436616] [<ffffffff8169036e>] smp_apic_timer_interrupt+0x6e/0x99
[58377.436618] [<ffffffff8168f74a>] apic_timer_interrupt+0x6a/0x70
[58377.436619] <EOI> [<ffffffff816855cc>] ? __schedule+0x3ac/0x750
[58377.436625] [<ffffffff8100b1fd>] ? mwait_idle+0xad/0x1f0
[58377.436627] [<ffffffff8100a743>] cpu_idle+0xb3/0x100
[58377.436629] [<ffffffff816736a2>] rest_init+0x72/0x80
[58377.436633] [<ffffffff81cc7d0e>] start_kernel+0x3ac/0x3b9
[58377.436635] [<ffffffff81cc7790>] ? repair_env_string+0x5b/0x5b
[58377.436636] [<ffffffff81cc732d>] x86_64_start_reservations+0x131/0x136
[58377.436638] [<ffffffff81cc741f>] x86_64_start_kernel+0xed/0xf4
[58377.436639] ---[ end trace 9e57364162374433 ]---
^ pretty sure that's the WARN_ON_ONCE(1)
Then a short while later the usual:
[58394.689801] ------------[ cut here ]------------
[58394.689817] WARNING: at net/sched/sch_generic.c:254
dev_watchdog+0x258/0x270()
[58394.689820] Hardware name: X9DR3-F
[58394.689836] NETDEV WATCHDOG: eth2 (ixgbe): transmit queue 14 timed out
[58394.689837] Modules linked in: bridge coretemp ghash_clmulni_intel
ipmi_watchdog ipmi_devintf gpio_ich microcode ixgbe sb_edac edac_core mei
lpc_ich mfd_core mdio ipmi_si ipmi_msghandler iptable_nat nf_nat_ipv4
nf_nat isci libsas igb ptp pps_core
[58394.689853] Pid: 0, comm: swapper/0 Tainted: G W
3.8.2 #3
[58394.689854] Call Trace:
[58394.689856] <IRQ> [<ffffffff8104964f>] warn_slowpath_common+0x7f/0xc0
[58394.689863] [<ffffffff81049746>] warn_slowpath_fmt+0x46/0x50
[58394.689865] [<ffffffff815a1508>] dev_watchdog+0x258/0x270
[58394.689868] [<ffffffff815a12b0>] ? __netdev_watchdog_up+0x80/0x80
[58394.689872] [<ffffffff81059259>] call_timer_fn+0x49/0x130
[58394.689875] [<ffffffff8107a07f>] ? scheduler_tick+0x15f/0x190
[58394.689877] [<ffffffff81059854>] run_timer_softirq+0x224/0x290
[58394.689880] [<ffffffff81058f76>] ? update_process_times+0x76/0x90
[58394.689882] [<ffffffff815a12b0>] ? __netdev_watchdog_up+0x80/0x80
[58394.689884] [<ffffffff8108ebd4>] ? ktime_get+0x54/0xe0
[58394.689886] [<ffffffff810518a7>] __do_softirq+0xc7/0x230
[58394.689890] [<ffffffff8168fd4c>] call_softirq+0x1c/0x30
[58394.689894] [<ffffffff81004415>] do_softirq+0x55/0x90
[58394.689895] [<ffffffff810516a5>] irq_exit+0x85/0xa0
[58394.689898] [<ffffffff8169036e>] smp_apic_timer_interrupt+0x6e/0x99
[58394.689900] [<ffffffff8168f74a>] apic_timer_interrupt+0x6a/0x70
[58394.689901] <EOI> [<ffffffff816855cc>] ? __schedule+0x3ac/0x750
[58394.689907] [<ffffffff8100b1fd>] ? mwait_idle+0xad/0x1f0
[58394.689909] [<ffffffff8100a743>] cpu_idle+0xb3/0x100
[58394.689911] [<ffffffff816736a2>] rest_init+0x72/0x80
[58394.689915] [<ffffffff81cc7d0e>] start_kernel+0x3ac/0x3b9
[58394.689917] [<ffffffff81cc7790>] ? repair_env_string+0x5b/0x5b
[58394.689918] [<ffffffff81cc732d>] x86_64_start_reservations+0x131/0x136
[58394.689920] [<ffffffff81cc741f>] x86_64_start_kernel+0xed/0xf4
[58394.689922] ---[ end trace 9e57364162374434 ]---
[58394.689965] ixgbe 0000:83:00.0 eth2: Reset adapter
[58447.665326] INFO: rcu_sched self-detected stall on CPU { 8} (t=15001
jiffies g=3607787 c=3607786 q=332913)
(then tons of stuck processes getting timed out)
next prev parent reply other threads:[~2013-03-14 23:15 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
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 [this message]
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=alpine.DEB.2.02.1303141610490.16308@dflat \
--to=dormando@rydia.net \
--cc=eric.dumazet@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).