From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH] mptcp: bugfix for RM_ADDR option parsing
Date: Mon, 08 Jun 2020 18:59:29 +0800 [thread overview]
Message-ID: <20200608105929.GA24487@OptiPlex> (raw)
In-Reply-To: 41246875-febc-e88d-304b-2a6692f590ac@tessares.net
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
On Mon, Jun 08, 2020 at 12:10:23PM +0200, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 08/06/2020 09:48, Geliang Tang wrote:
> > In MPTCPOPT_RM_ADDR option parsing, the pointer "ptr" pointed to the
> > "Subtype" octet, the pointer "ptr+1" pointed to the "Address ID" octet:
> >
> > +-------+-------+---------------+
> > |Subtype|(resvd)| Address ID |
> > +-------+-------+---------------+
> > | |
> > ptr ptr+1
> >
> > We should set mp_opt->rm_id to the value of "ptr+1", not "ptr". This patch
> > will fix this bug.
>
> Thank you for the patch, good catch!
> Indeed "ptr" should be incremented.
>
> Because this is a bug-fix for net, may you clearly indicate that in the
> subject to help -net maintainers please? [PATCH net v2]
>
> Also, may you add a "Fixes" tag as well as it is for -net ? I guess it
> should be:
>
> Fixes: 3df523ab582c ("mptcp: Add ADD_ADDR handling")
>
> The rest is good!
>
> 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
Hi Matt,
Thanks for your reply.
I have already resend patch v2 to you.
-Geliang
WARNING: multiple messages have this Message-ID (diff)
From: Geliang Tang <geliangtang@gmail.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Mat Martineau <mathew.j.martineau@linux.intel.com>,
Matthieu Baerts <matthieu.baerts@tessares.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Peter Krystad <peter.krystad@linux.intel.com>,
netdev@vger.kernel.org, mptcp@lists.01.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mptcp: bugfix for RM_ADDR option parsing
Date: Mon, 8 Jun 2020 18:59:29 +0800 [thread overview]
Message-ID: <20200608105929.GA24487@OptiPlex> (raw)
In-Reply-To: <41246875-febc-e88d-304b-2a6692f590ac@tessares.net>
On Mon, Jun 08, 2020 at 12:10:23PM +0200, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 08/06/2020 09:48, Geliang Tang wrote:
> > In MPTCPOPT_RM_ADDR option parsing, the pointer "ptr" pointed to the
> > "Subtype" octet, the pointer "ptr+1" pointed to the "Address ID" octet:
> >
> > +-------+-------+---------------+
> > |Subtype|(resvd)| Address ID |
> > +-------+-------+---------------+
> > | |
> > ptr ptr+1
> >
> > We should set mp_opt->rm_id to the value of "ptr+1", not "ptr". This patch
> > will fix this bug.
>
> Thank you for the patch, good catch!
> Indeed "ptr" should be incremented.
>
> Because this is a bug-fix for net, may you clearly indicate that in the
> subject to help -net maintainers please? [PATCH net v2]
>
> Also, may you add a "Fixes" tag as well as it is for -net ? I guess it
> should be:
>
> Fixes: 3df523ab582c ("mptcp: Add ADD_ADDR handling")
>
> The rest is good!
>
> Cheers,
> Matt
> --
> Matthieu Baerts | R&D Engineer
> matthieu.baerts@tessares.net
> Tessares SA | Hybrid Access Solutions
> www.tessares.net
> 1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium
Hi Matt,
Thanks for your reply.
I have already resend patch v2 to you.
-Geliang
next reply other threads:[~2020-06-08 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 10:59 Geliang Tang [this message]
2020-06-08 10:59 ` [PATCH] mptcp: bugfix for RM_ADDR option parsing Geliang Tang
-- strict thread matches above, loose matches on Subject: below --
2020-06-08 10:10 [MPTCP] " Matthieu Baerts
2020-06-08 10:10 ` Matthieu Baerts
2020-06-08 7:48 [MPTCP] " Geliang Tang
2020-06-08 7:48 ` Geliang Tang
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=20200608105929.GA24487@OptiPlex \
--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.