From: Neal Cardwell <ncardwell@google.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Yuchung Cheng <ycheng@google.com>,
netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
James Morris <jmorris@namei.org>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [REGRESSION] tcp/ipv4: kernel panic because of (possible) division by zero
Date: Sun, 10 Jan 2016 09:54:16 -0500 [thread overview]
Message-ID: <CADVnQykvDhCrCuFR0MCiEvD7DUbf+ZVBOysa1iWSE6-FydzqYQ@mail.gmail.com> (raw)
In-Reply-To: <CADVnQy=S62KoQL7thY73Kb=1Qd60drvOHJhE8UwH9qzPFOadEg@mail.gmail.com>
On Sun, Jan 10, 2016 at 9:48 AM, Neal Cardwell <ncardwell@google.com> wrote:
> On Sun, Jan 10, 2016 at 5:23 AM, Oleksandr Natalenko
> <oleksandr@natalenko.name> wrote:
>> With the patch queued for upstream and ECN enabled I get WARN_ON_ONCE()
>> triggered. Here is the stacktrace:
>>
>> https://gist.github.com/89203e77bfcb051f269a
>>
>> It seems that tp->prior_cwnd is zero.
>
> Hmm. Interesting. Can you please confirm that you are using the cubic
> congestion control module?
Would you be able to do an experiment where you reboot, and then
disable ECN upon startup, and then see if the warning still shows up
without ECN?
thanks,
neal
next prev parent reply other threads:[~2016-01-10 14:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 20:25 [REGRESSION] tcp/ipv4: kernel panic because of (possible) division by zero Oleksandr Natalenko
2015-12-22 2:10 ` Yuchung Cheng
2015-12-22 20:13 ` Oleksandr Natalenko
2016-01-06 16:50 ` Oleksandr Natalenko
2016-01-06 18:19 ` Yuchung Cheng
2016-01-06 18:43 ` Yuchung Cheng
2016-01-06 18:49 ` Oleksandr Natalenko
2016-01-09 17:34 ` Oleksandr Natalenko
2016-01-10 10:23 ` Oleksandr Natalenko
2016-01-10 14:48 ` Neal Cardwell
2016-01-10 14:54 ` Neal Cardwell [this message]
2016-01-10 14:57 ` Oleksandr Natalenko
2016-01-10 14:57 ` Oleksandr Natalenko
2016-01-10 17:29 ` Neal Cardwell
2016-01-10 17:50 ` Oleksandr Natalenko
2016-01-10 18:00 ` Neal Cardwell
2016-01-10 21:56 ` Oleksandr Natalenko
2016-01-11 18:47 ` Neal Cardwell
2016-01-11 23:26 ` Oleksandr Natalenko
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=CADVnQykvDhCrCuFR0MCiEvD7DUbf+ZVBOysa1iWSE6-FydzqYQ@mail.gmail.com \
--to=ncardwell@google.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=ycheng@google.com \
--cc=yoshfuji@linux-ipv6.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).