From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: lkml@techboom.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: kernel BUG at net/ipv4/tcp_output.c:1006!
Date: Fri, 13 May 2011 16:01:38 -0400 (EDT) [thread overview]
Message-ID: <20110513.160138.1477780250019480052.davem@davemloft.net> (raw)
In-Reply-To: <1305316058.3120.6.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 13 May 2011 21:47:38 +0200
> I suspect we should push commit 2fceec13375e5d98 (tcp: len check is
> unnecessarily devastating, change to WARN_ON) to stable if not already
> done...
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=2fceec13375e5d98
>
> David, is this commit in your stable queue ?
No, but now it is.
next prev parent reply other threads:[~2011-05-13 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 17:11 kernel BUG at net/ipv4/tcp_output.c:1006! TB
2011-05-13 17:20 ` Ben Greear
2011-05-13 17:27 ` Eric Dumazet
2011-05-13 19:30 ` TB
2011-05-13 19:47 ` Eric Dumazet
2011-05-13 20:01 ` David Miller [this message]
2011-05-19 17:08 ` TB
2011-05-19 17:11 ` Eric Dumazet
2011-05-24 16:09 ` TB
2011-05-24 16:20 ` Eric Dumazet
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=20110513.160138.1477780250019480052.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@techboom.com \
--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).