netdev - Re: [PATCH net-next 0/3] net: introduce IFF_PROTO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150320.181536.662222674547158857.davem@davemloft.net>
Date:	Fri, 20 Mar 2015 18:15:36 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	anuradhak@...ulusnetworks.com
Cc:	netdev@...r.kernel.org, roopa@...ulusnetworks.com,
	gospo@...ulusnetworks.com, wkok@...ulusnetworks.com
Subject: Re: [PATCH net-next 0/3] net: introduce IFF_PROTO_DOWN flag.

From: Anuradha Karuppiah <anuradhak@...ulusnetworks.com>
Date: Fri, 20 Mar 2015 14:16:26 -0700

> What we are looking for is a way for user space to hold the device
> down on detecting incorrect config/topology and for enabling the
> device once the error condition is removed provided the administrator
> didn’t intentionally disable it. And we don't see a way for a user
> protocol to do this without involving the kernel.

It is not your business to override what the administrator asks for.

This is what I mean by "cooperative".

ip link up has no idea about your error states, neither does every
administrator out there.

So you're changing behavior in an incompatible way.

This is why you need a wholistic approach in userland that propagates
this knowledge all around, rather than just using a sledge hammer by
asking the kernel to enforce some new rule upon unsuspecting existing
users.