From: Stephen Hemminger <stephen@networkplumber.org>
To: anuradhak@cumulusnetworks.com
Cc: davem@davemloft.net, sfeldma@gmail.com, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, gospo@cumulusnetworks.com,
wkok@cumulusnetworks.com
Subject: Re: [RFC PATCH net-next v3 1/4] net core: Add IFF_PROTO_DOWN support.
Date: Wed, 29 Apr 2015 15:13:36 -0700 [thread overview]
Message-ID: <20150429151336.0d6d8aab@urahara> (raw)
In-Reply-To: <1430156304-13187-2-git-send-email-anuradhak@cumulusnetworks.com>
On Mon, 27 Apr 2015 10:38:21 -0700
anuradhak@cumulusnetworks.com wrote:
> From: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
>
> This patch introduces an IFF_PROTO_DOWN flag that can be used by
> user space applications to notify drivers that errors have been
> detected on the device.
>
> Signed-off-by: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
> Signed-off-by: Andy Gospodarek <gospo@cumulusnetworks.com>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
> Signed-off-by: Wilson Kok <wkok@cumulusnetworks.com>
I worry that adding another bit to an already complex state API
will break userspace.
There are lots of things besides iproute2 which look at those
flags including routing daemons (quagga), network manager, netplugd,
and switch controllers.
next prev parent reply other threads:[~2015-04-29 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 17:38 [RFC PATCH net-next v3 1/4] net core: Add IFF_PROTO_DOWN support anuradhak
2015-04-28 6:05 ` Scott Feldman
2015-04-28 15:45 ` Anuradha Karuppiah
2015-04-29 22:13 ` Stephen Hemminger [this message]
2015-04-29 23:07 ` Anuradha Karuppiah
2015-04-29 23:25 ` Anuradha Karuppiah
2015-04-29 23:33 ` Stephen Hemminger
2015-04-30 0:16 ` Anuradha Karuppiah
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=20150429151336.0d6d8aab@urahara \
--to=stephen@networkplumber.org \
--cc=anuradhak@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=wkok@cumulusnetworks.com \
/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