netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: "Paweł Staszewski" <pstaszewski@itcare.pl>,
	dmichail@google.com,
	"Linux Kernel Network Developers" <netdev@vger.kernel.org>
Subject: Re: Latest net-next kernel 4.19.0+
Date: Tue, 30 Oct 2018 10:50:10 -0700	[thread overview]
Message-ID: <473bee73-b40e-2038-35e2-2c03482f7b75@gmail.com> (raw)
In-Reply-To: <CAM_iQpUKTh51maAzht8M3LuJAYDRMRnsGn_+Db0rGG-scW2SnA@mail.gmail.com>



On 10/30/2018 10:32 AM, Cong Wang wrote:

> Unlike Pawel's case, we don't use vlan at all, maybe this is why we see
> it much less frequently than Pawel.
> 
> Also, it is probably not specific to mlx5, as there is another report which
> is probably a non-mlx5 driver.

Not sure if you provided a stack trace ?

Have you tried IPv6 frags maybe ?

  reply	other threads:[~2018-10-31  2:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30  0:10 Latest net-next kernel 4.19.0+ Paweł Staszewski
2018-10-30  0:11 ` Paweł Staszewski
2018-10-30  0:34   ` Paweł Staszewski
2018-10-30  2:27   ` Cong Wang
2018-10-30  2:43     ` Cong Wang
2018-10-30  2:53     ` Eric Dumazet
2018-10-30  3:52       ` Eric Dumazet
2018-10-30  6:09         ` Dimitris Michailidis
2018-10-30  7:29           ` Eric Dumazet
2018-10-30  8:09             ` Paweł Staszewski
2018-10-30 14:16               ` Eric Dumazet
2018-10-30 17:32                 ` Cong Wang
2018-10-30 17:50                   ` Eric Dumazet [this message]
2018-10-30 17:54                     ` Cong Wang
2018-10-31 21:05                   ` Saeed Mahameed
2018-10-31 21:17                     ` Cong Wang
2018-11-01 22:59                       ` Paweł Staszewski
2018-11-08 18:35                         ` Cong Wang
2018-10-31 21:22                     ` Paweł Staszewski
2018-10-31 21:24                 ` Paweł Staszewski

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=473bee73-b40e-2038-35e2-2c03482f7b75@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=dmichail@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pstaszewski@itcare.pl \
    --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).