From: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
To: Scott Feldman <sfeldma@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
Andy Gospodarek <gospo@cumulusnetworks.com>,
Wilson Kok <wkok@cumulusnetworks.com>
Subject: Re: [RFC PATCH net-next v3 1/4] net core: Add IFF_PROTO_DOWN support.
Date: Tue, 28 Apr 2015 08:45:50 -0700 [thread overview]
Message-ID: <CACcJQnQOei+1Gkc_-1hZ1aFD+3EgFRprUBmqOFWKPh6hcuSvGw@mail.gmail.com> (raw)
In-Reply-To: <CAE4R7bBv350WnC4uEp7YZy7Jpq0zaTouWysgbSHXyktwTA9voA@mail.gmail.com>
On Mon, Apr 27, 2015 at 11:05 PM, Scott Feldman <sfeldma@gmail.com> wrote:
> On Mon, Apr 27, 2015 at 10:38 AM, <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>
>> ---
>> include/uapi/linux/if.h | 4 ++++
>> net/8021q/vlan_dev.c | 3 ++-
>> net/core/dev.c | 2 +-
>> 3 files changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/uapi/linux/if.h b/include/uapi/linux/if.h
>> index 9cf2394..e263bd2 100644
>> --- a/include/uapi/linux/if.h
>> +++ b/include/uapi/linux/if.h
>> @@ -66,6 +66,8 @@
>> * @IFF_LOWER_UP: driver signals L1 up. Volatile.
>> * @IFF_DORMANT: driver signals dormant. Volatile.
>> * @IFF_ECHO: echo sent packets. Volatile.
>> + * @IFF_PROTO_DOWN: protocol is down on the interface. Can be toggled
>> + * through sysfs.
>
> This comment is stale, right? I didn't see any sysfs support in the patchset.
Correct, No new sysfs has been added for this flag. But IFF_PROTO_DOWN
can be toggled via the already existing generic flags sysfs (similar
to say IFF_MULTICAST); hence the comment –
root@net-next:~# echo 0x81003 > /sys/class/net/eth0/flags
root@net-next:~# cat /sys/class/net/eth0/flags
0x81003
next prev parent reply other threads:[~2015-04-28 15:45 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 [this message]
2015-04-29 22:13 ` Stephen Hemminger
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=CACcJQnQOei+1Gkc_-1hZ1aFD+3EgFRprUBmqOFWKPh6hcuSvGw@mail.gmail.com \
--to=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;
as well as URLs for NNTP newsgroup(s).