linux-kernel - Re: asix usb network driver: nfg

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]

Date:	Wed, 26 Oct 2011 21:23:15 -0400
From:	Mark Lord <kernel@...savvy.com>
To:	David Miller <davem@...emloft.net>
CC:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: asix usb network driver: nfg

On 11-10-26 07:40 PM, David Miller wrote:
> From: Mark Lord <kernel@...savvy.com>
> Date: Wed, 26 Oct 2011 19:36:18 -0400
> 
>> So, the in-kernel asix driver seems badly broken for a lot of hardware,
>> and the vendor driver also has a slight race somewhere that is cured
>> by enabling debug logging.
>>
>> Is there an asix driver maintainer, or anyone else with the time
>> to step up and try to fix these issues?
> 
> The issues you speak of are well known for at least two years but
> nobody wants to work on this.

Okay, that's useful to know.

I think I may be able to get some funding to take a crack at perhaps
figuring out the "DEBUG" race thing in the vendor's copy of the driver,
since that one seems to be in the better shape of the two.

Any strong advance objections to replacing the in-kernel version
with a (fixed) vendor open source version?

It appears that the two share a common heritage, but somewhere along the
line the in-kernel one stopped being maintained as well as the external one.

Assuming I get approval, I'll try and fix the vendor version,
tidy it up to pass checkpatch.pl with flying colours,
and then submit the resulting diff to you.

Hopeless, or would you perhaps accept such a wholesale change?

Thanks David.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/