From: Jiri Benc <jbenc@redhat.com>
To: Matthias Schiffer <mschiffer@universe-factory.net>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] vxlan: correctly validate VXLAN ID against VXLAN_N_VID
Date: Thu, 23 Feb 2017 17:26:16 +0100 [thread overview]
Message-ID: <20170223172616.50111b3a@griffin> (raw)
In-Reply-To: <4650647d72b8f219cb725b40de9b4627f3306919.1487866739.git.mschiffer@universe-factory.net>
On Thu, 23 Feb 2017 17:19:41 +0100, Matthias Schiffer wrote:
> The incorrect check caused an off-by-one error: the maximum VID 0xffffff
> was unusable.
>
> Fixes: d342894c5d2f ("vxlan: virtual extensible lan")
> Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
> ---
> v2: check against VXLAN_N_VID instead of changing operator
Acked-by: Jiri Benc <jbenc@redhat.com>
Thanks!
Jiri
next prev parent reply other threads:[~2017-02-23 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 16:19 [PATCH net v2] vxlan: correctly validate VXLAN ID against VXLAN_N_VID Matthias Schiffer
2017-02-23 16:26 ` Jiri Benc [this message]
2017-02-24 16:20 ` David Miller
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=20170223172616.50111b3a@griffin \
--to=jbenc@redhat.com \
--cc=davem@davemloft.net \
--cc=mschiffer@universe-factory.net \
--cc=netdev@vger.kernel.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).