netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Girish Moodalbail <girish.moodalbail@oracle.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2 v2 1/1] vxlan: Add support for modifying vxlan device attributes
Date: Thu, 11 May 2017 11:12:22 -0700	[thread overview]
Message-ID: <20170511111222.5edc4b0c@xeon-e3> (raw)
In-Reply-To: <1494095863-21916-2-git-send-email-girish.moodalbail@oracle.com>

On Sat,  6 May 2017 11:37:43 -0700
Girish Moodalbail <girish.moodalbail@oracle.com> wrote:

> Ability to change vxlan device attributes was added to kernel through
> commit 8bcdc4f3a20b ("vxlan: add changelink support"), however one
> cannot do the same through ip(8) command.  Changing the allowed vxlan
> device attributes using 'ip link set dev <vxlan_name> type vxlan
> <allowed_attributes>' currently fails with 'operation not supported'
> error.  This failure is due to the incorrect rtnetlink message
> construction for the 'ip link set' operation.
> 
> The vxlan_parse_opt() callback function is called for parsing options
> for both 'ip link add' and 'ip link set'. For the 'add' case, we pass
> down default values for those attributes that were not provided as CLI
> options. However, for the 'set' case we should be only passing down the
> explicitly provided attributes and not any other (default) attributes.
> 
> Signed-off-by: Girish Moodalbail <girish.moodalbail@oracle.com>

I like this much better.
Applied, Thanks.

      parent reply	other threads:[~2017-05-11 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 18:37 [PATCH iproute2 v2 0/1] vxlan: support for modifying vxlan device Girish Moodalbail
2017-05-06 18:37 ` [PATCH iproute2 v2 1/1] vxlan: Add support for modifying vxlan device attributes Girish Moodalbail
2017-05-07 14:40   ` Roman Mashak
2017-05-10  7:31     ` Girish Moodalbail
2017-05-11 18:12   ` 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=20170511111222.5edc4b0c@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=girish.moodalbail@oracle.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;
as well as URLs for NNTP newsgroup(s).