All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [PATCH] mptcp: do not warn when replacing an identical mapping.
Date: Wed, 05 Jun 2019 19:42:16 +0200	[thread overview]
Message-ID: <243078b8-e0d3-f7f1-e021-68bec0ffdd34@tessares.net> (raw)
In-Reply-To: 87926986ed8572ddad3c82230f0cf9b883fbbeb9.1559742173.git.pabeni@redhat.com

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

Hi Paolo,

On 05/06/2019 15:53, Paolo Abeni wrote:
> Said event can happen due GSO/TSO, do not warn then.
> 
> Fixes: af798ed636e2 ("mptcp: Implement MPTCP receive path")
> Signed-off-by: Paolo Abeni <pabeni(a)redhat.com>
> --
> Notes:
> - I'm ok squashing this commit into the fixed one
> - I can't reproduce the warn locally, need someone else to verify 
>   this one

Thank you for the patch! It looks good to me but I would prefer to wait
for Mat's review on that as he identified the cause.

I tested it locally with the virtme' script and I no longer have the
warning in dmesg!

Cheers,
Matt
-- 
Matthieu Baerts | R&D Engineer
matthieu.baerts(a)tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium

             reply	other threads:[~2019-06-05 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 17:42 Matthieu Baerts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-06 12:05 [MPTCP] [PATCH] mptcp: do not warn when replacing an identical mapping Matthieu Baerts
2019-06-05 21:31 Mat Martineau
2019-06-05 13:53 Paolo Abeni

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=243078b8-e0d3-f7f1-e021-68bec0ffdd34@tessares.net \
    --to=unknown@example.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 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.