From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netdev@vger.kernel.org
Subject: Re: [iproute PATCH v3 0/3] Check user supplied interface name lengths
Date: Mon, 2 Oct 2017 08:03:09 -0700 [thread overview]
Message-ID: <20171002080309.1d7f4099@xeon-e3> (raw)
In-Reply-To: <20171002114637.25703-1-phil@nwl.cc>
On Mon, 2 Oct 2017 13:46:34 +0200
Phil Sutter <phil@nwl.cc> wrote:
> This series adds explicit checks for user-supplied interface names to
> make sure they fit Linux's requirements.
>
> The first two patches simplify interface name parsing in some places -
> these are side-effects of working on the actual implementation provided
> in patch three.
>
> Changes since v2:
> - Changed patch 3 as suggested in review.
>
> Changes since v1:
> - Patches 1 and 2 introduced.
> - Changes to patch 3 are listed in there.
>
> Phil Sutter (3):
> ip{6,}tunnel: Avoid copying user-supplied interface name around
> tc: flower: No need to cache indev arg
> Check user supplied interface name lengths
>
> include/utils.h | 2 ++
> ip/ip6tunnel.c | 9 +++++----
> ip/ipl2tp.c | 4 +++-
> ip/iplink.c | 31 ++++++++++++-------------------
> ip/ipmaddr.c | 3 ++-
> ip/iprule.c | 10 ++++++++--
> ip/iptunnel.c | 29 +++++++++++++++--------------
> ip/iptuntap.c | 6 ++++--
> lib/utils.c | 29 +++++++++++++++++++++++++++++
> misc/arpd.c | 3 ++-
> tc/f_flower.c | 7 +++----
> 11 files changed, 85 insertions(+), 48 deletions(-)
>
Applied.
prev parent reply other threads:[~2017-10-02 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 11:46 [iproute PATCH v3 0/3] Check user supplied interface name lengths Phil Sutter
2017-10-02 11:46 ` [iproute PATCH v3 1/3] ip{6,}tunnel: Avoid copying user-supplied interface name around Phil Sutter
2017-10-02 11:46 ` [iproute PATCH v3 2/3] tc: flower: No need to cache indev arg Phil Sutter
2017-10-02 11:46 ` [iproute PATCH v3 3/3] Check user supplied interface name lengths Phil Sutter
2017-10-02 15:03 ` Stephen Hemminger [this message]
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=20171002080309.1d7f4099@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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).