netdev - Re: Fwd: [ofa-general] FW: QLogic vNIC Kernel Submission

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 for Android: free password hash cracker in your pocket

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

Message-ID: <48582340.7010409@trash.net>
Date:	Tue, 17 Jun 2008 22:49:04 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	John Russo <john.russo@...gic.com>
CC:	shemminger@...tta.com,
	"Amar Mudrankit (Contractor - )" <amar.mudrankit@...gic.com>,
	netdev@...r.kernel.org, rdreier@...co.com,
	"Kuchimanchi, Ramachandra \(Contractor - \)" 
	<ramachandra.kuchimanchi@...gic.com>,
	"Poornima Kamath (Contractor - )" <poornima.kamath@...gic.com>
Subject: Re: Fwd: [ofa-general] FW: QLogic vNIC Kernel Submission

John Russo wrote:
>>> As Patrick said, there is also a sense of doing the right thing. The 
>>> developers would rather not repeat past mistakes, so are naturally 
>>> hesitant on API's.
>>>       
>
> I completely understand the sense of doing the right thing. That is why
> we put in the effort to migrate our code to sysfs in the first place.
> We had a different solution but agreed to change it to meet the
> guidelines of other contributors to the InfiniBand (OFED) stack.  What I
> can't understand is the ease of which some people say "let's just change
> to this great new design even if it means a large rewrite of existing
> code which may increase the likelihood of injecting errors".  I
> apologize if I come off as being agitated but it is very frustrating to
> spend time and effort attempting to conform to a groups requests only to
> have it changed at the end. 
>   

Frankly, you didn't even try to fix the most obvious mistakes in your
interface, like duplication of existing interfaces (csum settings)
and very unusual behaviour (state machine triggered device registation)
before you started complaining (and both of these are *really* easy to
do).

That you were asked to migrate to sysfs is unfortunate. The fact is
though that your driver is a virtual ethernet device, not an infiniband
device, so it should use the proper APIs for this kind of device. Work
has been going on for years to provide a uniform interface to the network
and your interface is a move in the opposite direction.


--
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