linux-kernel - Re: pull request: wireless-2.6 2008-11-18

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: <20081119143919.GA3485@tuxdriver.com>
Date:	Wed, 19 Nov 2008 09:39:19 -0500
From:	"John W. Linville" <linville@...driver.com>
To:	Tomas Winkler <tomasw@...il.com>
Cc:	davem@...emloft.net, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	sfr@...b.auug.org.au
Subject: Re: pull request: wireless-2.6 2008-11-18

On Wed, Nov 19, 2008 at 11:34:37AM +0200, Tomas Winkler wrote:
> On Wed, Nov 19, 2008 at 8:46 AM, Tomas Winkler <tomasw@...il.com> wrote:
> > On Wed, Nov 19, 2008 at 2:07 AM, John W. Linville
> > <linville@...driver.com> wrote:

> >>      mac80211: remove ieee80211_notify_mac
> >>      iwlagn: fix RX skb alignment
> >
> > IMHO its premature pushing ttese 2 patches up, they came in yestrday
> > and nobody here has run tthe code

Well, thanks for your opinion.  Here is mine:

The iwlwifi drivers have been hitting these problems for months,
and I have seen no effort by your team to address the problems.
It is possible that your team is working on them behind closed doors
and will eventually throw something over the wall to us.  I'm tired
of waiting for that, and I imagine that hordes of iwlagn users are
tired of waiting as well.

Johannes has presented us with plausible fixes, and people are
reporting that the patches work for them.  I can merge these patches,
or wait/hope/pray for some to come from your team.  Experience suggests
that if fixes do come from your team that they will either be buried
in some monster patch that largely addresses something else, or
that the patches will arrive with a changelog that is terse and/or
unintelligble.  Subsequently, I am not optimistic about waiting.

I think Johannes cited four different bugzilla.kernel.org entries
between those two patches.  What is your team doing to address
those bugs?

Obviously, I still think that those patches should be merged.

> Just checked our bug database,  the ieee80211_notify_mac was
> introduced mainly to overcome HW bug when
> receiver become deaf  in heavy traffic such as ftp in noisy
> environment. Otherwise reconnection was too slow to keep ftp going. We
> need to check whether we are still hitting this before applying
> removal this function

You are welcome to submit patches that address your hardware issue
and which do not introduce locking problems.

Thanks,

John
-- 
John W. Linville		Linux should be at the core
linville@...driver.com			of your literate lifestyle.
--
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/