From: "Bjørn Mork" <bjorn@mork.no>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>, netdev@vger.kernel.org
Subject: Re: v3.8.5: "TCP: snd_cwnd is nul, please report this bug."
Date: Mon, 08 Apr 2013 17:42:29 +0200 [thread overview]
Message-ID: <87wqsdghay.fsf@nemi.mork.no> (raw)
In-Reply-To: <1365434301.3887.14.camel@edumazet-glaptop> (Eric Dumazet's message of "Mon, 08 Apr 2013 08:18:21 -0700")
Eric Dumazet <eric.dumazet@gmail.com> writes:
> I believe patch applies (with some fuzz) on Linus tree, and maybe on 3.8
> too.
Probably just a minor context issue, but it failed like this on v3.9-rc6
(as well as 'net' and v3.8.6):
Applying: v3.8.5: "TCP: snd_cwnd is nul, please report this bug."
error: patch failed: net/ipv4/tcp_westwood.c:233
error: net/ipv4/tcp_westwood.c: patch does not apply
I'll just run todays net-next with this on top. No problem.
Bjørn
next prev parent reply other threads:[~2013-04-08 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:06 v3.8.5: "TCP: snd_cwnd is nul, please report this bug." Bjørn Mork
2013-04-08 14:30 ` Eric Dumazet
2013-04-08 15:14 ` Bjørn Mork
2013-04-08 15:18 ` Eric Dumazet
2013-04-08 15:42 ` Bjørn Mork [this message]
2013-06-02 10:19 ` Bjørn Mork
2013-06-02 14:22 ` Eric Dumazet
2013-06-02 14:24 ` Eric Dumazet
2013-06-02 19:21 ` Bjørn Mork
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=87wqsdghay.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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