From: Thomas Haller <thaller@redhat.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, stephen@networkplumber.org,
dcbw@redhat.com
Subject: Re: [PATCH v2 2/2] ipv6 addrconf: don't cleanup route prefix for IFA_F_NOPREFIXROUTE
Date: Tue, 07 Jan 2014 19:32:57 +0100 [thread overview]
Message-ID: <1389119577.2248.16.camel@weing> (raw)
In-Reply-To: <20140107162847.GB30393@order.stressinduktion.org>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
On Tue, 2014-01-07 at 17:28 +0100, Hannes Frederic Sowa wrote:
> On Tue, Jan 07, 2014 at 03:39:13PM +0100, Thomas Haller wrote:
> > Also, when adding the NOPREFIXROUTE flag to an already existing address,
> > check if there there is a prefix that was likly added by the kernel
> > and delete it.
>
> Hmm, could you give a bit more details why you have done this? I find
> that a bit counterintuitive. Maybe it has a reason?
>
Hi,
You find the behavior or the commit message counterintuitive? Didn't you
suggest this behavior in your email from "7 Jan 2014 13:01:11 +0100"?
For v3 I will reword the commit message. How about the following:
ipv6 addrconf: don't cleanup prefix route for IFA_F_NOPREFIXROUTE
Refactor the deletion/update of prefix routes when removing an
address. Now, consider IFA_F_NOPREFIXROUTE and if there is an address
present with this flag, to not cleanup the route. Instead, assume
that userspace is taking care of this prefix.
Also perform the same cleanup, when userspace changes an existing address
to add NOPREFIXROUTE to an address that didn't have this flag. We do this
because when the address was added, a prefix route was created for it.
Since the user now wants to handle this route by himself, we remove it again.
As before, a prefix route only gets removed, if there is no address
that might need it. Or, if there are only non-permanent addresses,
update the lifetime of the route.
ciao,
Thomas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-01-07 18:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 15:34 [patch iproute2 v2 0/2] add support for IFA_F_MANAGETEMPADDR Jiri Pirko
2014-01-02 15:34 ` [patch iproute2 v2 1/2] add support for extended ifa_flags Jiri Pirko
2014-01-02 15:34 ` [patch iproute2 v2 2/2] add support for IFA_F_MANAGETEMPADDR Jiri Pirko
2014-01-02 15:50 ` [PATCH 1/1] fixup! " Thomas Haller
2014-01-04 10:44 ` Jiri Pirko
2014-01-02 17:29 ` [patch iproute2 v2 0/2] " Hannes Frederic Sowa
2014-01-04 10:43 ` Jiri Pirko
2014-01-04 10:55 ` Hannes Frederic Sowa
2014-01-04 11:05 ` Jiri Pirko
2014-01-04 11:15 ` Hannes Frederic Sowa
2014-01-04 11:21 ` Thomas Haller
2014-01-04 11:35 ` Hannes Frederic Sowa
2014-01-06 15:41 ` Thomas Haller
2014-01-06 16:01 ` Hannes Frederic Sowa
2014-01-06 17:29 ` [PATCH 1/1] ipv6 addrconf: add IFA_F_NOPREFIXROUTE flag to suppress creation of IP6 routes Thomas Haller
2014-01-06 17:38 ` Jiri Pirko
2014-01-07 9:39 ` Hannes Frederic Sowa
2014-01-07 12:01 ` Hannes Frederic Sowa
2014-01-07 12:14 ` Thomas Haller
2014-01-07 12:22 ` Hannes Frederic Sowa
2014-01-07 14:39 ` [PATCH v2 0/2] " Thomas Haller
2014-01-07 14:39 ` [PATCH v2 1/2] " Thomas Haller
2014-01-07 14:39 ` [PATCH v2 2/2] ipv6 addrconf: don't cleanup route prefix for IFA_F_NOPREFIXROUTE Thomas Haller
2014-01-07 16:28 ` Hannes Frederic Sowa
2014-01-07 18:32 ` Thomas Haller [this message]
2014-01-07 19:01 ` Hannes Frederic Sowa
2014-01-07 22:54 ` Thomas Haller
2014-01-07 23:09 ` Hannes Frederic Sowa
2014-01-07 16:03 ` [PATCH v2 0/2] ipv6 addrconf: add IFA_F_NOPREFIXROUTE flag to suppress creation of IP6 routes Hannes Frederic Sowa
2014-01-07 21:42 ` Thomas Haller
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=1389119577.2248.16.camel@weing \
--to=thaller@redhat.com \
--cc=dcbw@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).