From: Martin KaFai Lau <kafai@fb.com>
To: Jovi Zhangwei <jovi@cloudflare.com>, Eric Dumazet <edumazet@google.com>
Cc: <ncardwell@google.com>, <netdev@vger.kernel.org>,
<davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
<jmorris@namei.org>, <yoshfuji@linux-ipv6.org>, <kaber@trash.net>,
FB Kernel Team <kernel-team@fb.com>
Subject: Re: kernel warning in tcp_fragment
Date: Mon, 27 Jul 2015 16:19:48 -0700 [thread overview]
Message-ID: <20150727231947.GC2832181@devbig242.prn2.facebook.com> (raw)
In-Reply-To: <CABPcSqLrbCm92z23sSUf_0dLGZU5ZMHvzGxWkTxx0hH5KsBKQg@mail.gmail.com>
On Wed, Jul 22, 2015 at 11:55:35AM -0700, Jovi Zhangwei wrote:
> Sorry for disturbing, our production system(3.14 and 3.18 stable
> kernel) have many tcp_fragment warnings,
> the trace is same as below one which you discussed before.
>
> https://urldefense.proofpoint.com/v1/url?u=http://comments.gmane.org/gmane.linux.network/365658&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=%2Faj1ZOQObwbmtLwlDw3XzQ%3D%3D%0A&m=fQUME5h%2FYY3oZjXbnLC3z6TaEEcTBSCAji4PkNqFjq8%3D%0A&s=1527f3221a6f31cba9544e5ddaa20986aafe8be8c898b42c7e9ce5e68d3803d8
>
> But I didn't found the final solution in that mail thread, do you have
> any new ideas or patches on this warning?
I think the following points to the last discussion. We are currently using a
similar patch:
http://comments.gmane.org/gmane.linux.network/366549
Eric, any update on your findings? or you have already pushed a fix?
Thanks,
--Martin
next prev parent reply other threads:[~2015-07-27 23:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 18:55 kernel warning in tcp_fragment Jovi Zhangwei
2015-07-27 19:08 ` Jovi Zhangwei
2015-07-27 23:19 ` Martin KaFai Lau [this message]
2015-07-31 18:04 ` Jovi Zhangwei
2015-08-10 18:10 ` Jovi Zhangwei
2015-08-10 18:35 ` Neal Cardwell
2015-08-10 21:53 ` Jovi Zhangwei
2015-08-13 3:45 ` Martin KaFai Lau
2015-08-13 23:05 ` Jovi Zhangwei
2015-09-01 23:02 ` Grant Zhang
2015-09-14 18:12 ` Martin KaFai Lau
[not found] ` <CABPcSqJMS3oYLbL=Ns71ciF_9rcZNuZ0VceV=noaLJgV=LTAQQ@mail.gmail.com>
2015-09-14 18:15 ` Neal Cardwell
[not found] ` <CABPcSqJEoVAXk+PAZCWgD6LFV0Nxz7ON3CUuZZMgrcRQFLK44w@mail.gmail.com>
2015-10-19 10:57 ` Jovi Zhangwei
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=20150727231947.GC2832181@devbig242.prn2.facebook.com \
--to=kafai@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=jovi@cloudflare.com \
--cc=kaber@trash.net \
--cc=kernel-team@fb.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.