From: David Miller <davem@davemloft.net>
To: kjlx@templeofstupid.com
Cc: maheshb@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH] Ipvlan should return an error when an address is already in use.
Date: Sun, 01 Jan 2017 22:26:32 -0500 (EST) [thread overview]
Message-ID: <20170101.222632.843875843588487678.davem@davemloft.net> (raw)
In-Reply-To: <20161231041058.GC2448@templeofstupid.com>
From: Krister Johansen <kjlx@templeofstupid.com>
Date: Fri, 30 Dec 2016 20:10:58 -0800
> The ipvlan code already knows how to detect when a duplicate address is
> about to be assigned to an ipvlan device. However, that failure is not
> propogated outward and leads to a silent failure. This teaches the ip
> address addition functions how to report this error to the user
> applications so that a notifier chain failure during ip address addition
> will not appear to succeed when it actually has not.
>
> This can be especially useful if it is necessary to provision many
> ipvlans in containers. The provisioning software (or operator) can use
> this to detect situations where an ip address is unexpectedly in use.
>
> Signed-off-by: Krister Johansen <kjlx@templeofstupid.com>
Your patch isn't handling the case of primary address promotions,
which also issue NETDEV_UP events on these notifier chains.
But on a more basic level, it's extremely important that once you
start using the notifier_{from,to}_errno() handling for a notifier,
you must start doing so for all such cases of that notifier.
next prev parent reply other threads:[~2017-01-02 3:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 4:10 [PATCH] Ipvlan should return an error when an address is already in use Krister Johansen
2017-01-02 3:26 ` David Miller [this message]
2017-01-04 10:04 ` Krister Johansen
2017-06-08 20:12 ` [PATCH v2 net-next] " Krister Johansen
2017-06-09 16:26 ` David Miller
2017-06-09 17:13 ` Krister Johansen
2017-06-09 17:15 ` David Miller
2017-06-09 17:25 ` Krister Johansen
2017-01-03 15:50 ` [PATCH] " Aaron Conole
2017-01-03 15:55 ` David Miller
2017-01-03 19:24 ` Aaron Conole
2017-01-04 10:09 ` Krister Johansen
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=20170101.222632.843875843588487678.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kjlx@templeofstupid.com \
--cc=maheshb@google.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).