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: <20150521.153029.774385014187583893.davem@davemloft.net>
Date:	Thu, 21 May 2015 15:30:29 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	leedom@...lsio.com
Cc:	hariprasad@...lsio.com, netdev@...r.kernel.org,
	nirranjan@...lsio.com
Subject: Re: [PATCH net-next 1/3] cxgb4: Add support for loopback between
 VI of same port

From: Casey Leedom <leedom@...lsio.com>
Date: Thu, 21 May 2015 16:36:00 +0000

> I definitely understand the issue of wanting to avoid randomly
> different module parameters in various drivers which do similar
> things.  What we're looking for is a list of the acceptable ways for
> doing things ― especially when they don't fit current
> ethtool/ioctl() mechanisms.

The prevailing assumption is that it's OK to have configuration
settings that can't be undone.

And that's bogus from the beginning.

Drivers that have such situations are extremely painful for large
scale organizations, and I think you probably have no idea how
much of a huge hassle is created by features that can't be undone
or disabled at run time.

It is not feasible to reboot every machine in one's datacenter to turn
off a feature that's causing problems.  Yet that's what some large
scale organizations end up having to do, and it's COMPLETELY NOT
ACCEPTABLT that they have to do this.

So instead of trying to figure out ways to use things other than
ethtool, work instead to eliminate all situations where a feature
cannot be disabled/undone after probe time.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ