netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Haley <brian.haley@hp.com>
To: David Ahern <dsahern@gmail.com>, netdev@vger.kernel.org
Cc: Hannes Frederic Sowa <hannes@redhat.com>
Subject: Re: [PATCH] net: ipv6: Make address flushing on ifdown optional - v2
Date: Mon, 02 Feb 2015 12:38:19 -0500	[thread overview]
Message-ID: <54CFB60B.3060800@hp.com> (raw)
In-Reply-To: <1422504065-17445-1-git-send-email-dsahern@gmail.com>

On 01/28/2015 11:01 PM, David Ahern wrote:
> Currently, all ipv6 addresses are flushed when the interface is configured
> down, even static address:
> 
...
> diff --git a/include/linux/ipv6.h b/include/linux/ipv6.h
> index 2805062c013f..b91b7c8be023 100644
> --- a/include/linux/ipv6.h
> +++ b/include/linux/ipv6.h
> @@ -53,6 +53,7 @@ struct ipv6_devconf {
>  	__s32           ndisc_notify;
>  	__s32		suppress_frag_ndisc;
>  	__s32		accept_ra_mtu;
> +	__s32		flush_addr_on_down;
>  	void		*sysctl;
>  };
...
> diff --git a/include/uapi/linux/ipv6.h b/include/uapi/linux/ipv6.h
> index 437a6a4b125a..ed10d4ba8340 100644
> --- a/include/uapi/linux/ipv6.h
> +++ b/include/uapi/linux/ipv6.h
> @@ -170,6 +170,7 @@ enum {
>  	DEVCONF_ACCEPT_RA_FROM_LOCAL,
>  	DEVCONF_USE_OPTIMISTIC,
>  	DEVCONF_ACCEPT_RA_MTU,
> +	DEVCONF_FLUSH_ON_DOWN,

nit: DEVCONF_FLUSH_ADDR_ON_DOWN to match the name added to ipv6_devconf.

-Brian

  parent reply	other threads:[~2015-02-02 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29  4:01 [PATCH] net: ipv6: Make address flushing on ifdown optional - v2 David Ahern
2015-02-01  1:17 ` David Miller
2015-02-02 15:33 ` David Ahern
2015-02-02 17:38 ` Brian Haley [this message]
2015-02-02 23:10 ` Stephen Hemminger
2015-02-03  0:11   ` David Ahern
2015-02-03  0:18     ` Stephen Hemminger
2015-02-03 17:27     ` Stephen Hemminger

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=54CFB60B.3060800@hp.com \
    --to=brian.haley@hp.com \
    --cc=dsahern@gmail.com \
    --cc=hannes@redhat.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).