From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/4] ip vrf fixups
Date: Wed, 21 Dec 2016 16:09:56 -0800 [thread overview]
Message-ID: <20161221160956.4660a386@xeon-e3> (raw)
In-Reply-To: <1481832422-10267-1-git-send-email-dsa@cumulusnetworks.com>
On Thu, 15 Dec 2016 12:06:58 -0800
David Ahern <dsa@cumulusnetworks.com> wrote:
> Some minor cleanups to the 'ip vrf' command.
>
> Patch 1 moves the CGROUP_BPF hint to the failure of prog_load since it
> fails first.
>
> Patch 2 refactors ipvrf_identify. The action part is moved to a function
> that can be used standalone and in the process flipped to fopen/fgets for
> robustness should the cgroups file grow larger than 4k.
>
> Patch 3 fixes the path switching to "default" VRF.
>
> Patch 4 moves a task to default VRF when switching namespaces.
>
> David Ahern (4):
> ip vrf: Move kernel config hint to prog_load failure
> ip vrf: Refactor ipvrf_identify
> ip vrf: Fix reset to default VRF
> ip netns: Reset vrf to default VRF on namespace switch
>
> ip/ip_common.h | 1 +
> ip/ipnetns.c | 5 +++
> ip/ipvrf.c | 103 +++++++++++++++++++++++++++++++++++----------------------
> 3 files changed, 69 insertions(+), 40 deletions(-)
>
Applied thanks.
prev parent reply other threads:[~2016-12-22 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 20:06 [PATCH iproute2 0/4] ip vrf fixups David Ahern
2016-12-15 20:06 ` [PATCH iproute2 1/4] ip vrf: Move kernel config hint to prog_load failure David Ahern
2016-12-15 20:07 ` [PATCH iproute2 2/4] ip vrf: Refactor ipvrf_identify David Ahern
2016-12-15 20:07 ` [PATCH iproute2 3/4] ip vrf: Fix reset to default VRF David Ahern
2016-12-15 20:07 ` [PATCH iproute2 4/4] ip netns: Reset vrf to default VRF on namespace switch David Ahern
2016-12-22 0:09 ` 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=20161221160956.4660a386@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsa@cumulusnetworks.com \
--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