linux-kernel - Re: What is current sundance.c status

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-next>] [day] [month] [year] [list]

Message-Id: <20061011195540.06b2ef13.akpm@osdl.org>
Date:	Wed, 11 Oct 2006 19:55:40 -0700
From:	Andrew Morton <akpm@...l.org>
To:	"Jesse Huang" <jesse@...lus.com.tw>
Cc:	<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
	<jgarzik@...ox.com>
Subject: Re: What is current sundance.c status

On Thu, 12 Oct 2006 10:29:37 +0800
"Jesse Huang" <jesse@...lus.com.tw> wrote:

>     Would you tell me what is the current IP100A status? Should I re-generate patches again. Would it put into kernel or not?

I'm sitting on a copy of them.  I didn't send them to Jeff last time
because:

sundance-remove-txstartthresh-and-rxearlythresh.patch

 There's no description of what this patent issue is.

sundance-fix-tx-pause-bug-reset_tx-intr_handler.patch

 There's no description of the bug which got fixed, nor how this patch
 fixes it.

sundance-change-phy-address-search-from-phy=1-to-phy=0.patch

 There's a (small) possibility that this will break on hardware which
 _doesn't_ have a phy at address 0.

sundance-correct-initial-and-close-hardware-step.patch

 There's no real description of the bug which is being fixed, nor of how
 this patch fixes it.

sundance-solve-host-error-problem-in-low-performance-embedded.patch

 No description of what the "host error problem" is, nor of what causes
 it, nor of how this patch fixes it.

So generally these patches are a bit worrying, and it is hard to gauge what
their risk factor is.

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