linux-kernel - Re: Oops report for the week preceding June 16th, 2008

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:	Tue, 17 Jun 2008 15:41:05 -0400
From:	Dave Jones <davej@...hat.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Ingo Molnar <mingo@...e.hu>, David Miller <davem@...emloft.net>,
	arjan@...ux.intel.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	tglx@...utronix.de, linville@...driver.com, gregkh@...e.de
Subject: Re: Oops report for the week preceding June 16th, 2008

On Tue, Jun 17, 2008 at 09:24:14PM +0200, Johannes Berg wrote:
 > 
 > > i have no gripes about the current situation of wireless in linux-next, 
 > > other than it all came 1-2 years too late:
 > 
 > Clearly, you don't have a clue about wireless. I'll admit to being
 > pissed off by statements like this because I personally spent a lot of
 > time getting wireless code into shape for merging, and it took a long
 > time.
 > 
 > If we'd have merged the existing wireless drivers 2 years ago, we would
 > have (at least) four 802.11 stacks in the kernel now, at least two
 > legally questionable drivers (the ath5k legal situation would probably
 > never have been cleared up, acx100 still isn't), no uniform API so it
 > would be impossible to write userspace support tools etc.

FWIW, the fact that there's so much churn happening in wireless right
now is IMO, a sign of its health.  When I told John "commit whatever
wireless bits you think need to be in Fedora" many months back, I admit
I wasn't expecting as much churn as there has been.

It's been something of a double edged sword.  It's great that users are
getting the latest drivers & fixes, but at the same time, it means they
get exposed to all the latest breakage at the same time.
Given the volume of change occuring, cherry-picking isn't an enviable task,
so distros are stuck between this reality, or leaving users hanging until we
get to the next point release.

FWIW, wireless isn't unique in this regard. For eg, the last few months we've
always been shipping the latest ALSA bits rather than what's in kernel.org too,
for similar reasons -- when bugs appear, the developers want to know
"does it still happen with the latest bits?"

The situation isn't perfect, but I don't think it's quite as bleak
as Ingo painted it to be.

	Dave

-- 
http://www.codemonkey.org.uk
--
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/