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 02:26:52 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mingo@...e.hu
Cc:	arjan@...ux.intel.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	tglx@...utronix.de, linville@...driver.com, davej@...hat.com,
	gregkh@...e.de
Subject: Re: Oops report for the week preceding June 16th, 2008

From: Ingo Molnar <mingo@...e.hu>
Date: Tue, 17 Jun 2008 11:20:23 +0200

> When distros feel the need to add large and risky patches that IMO shows 
> process failure on our part and further isolates mainline from distros 
> and from testers.

You say this to the point where you sound like a broken record.  It's
a bit tiring, and nothing positive ever comes of these rants.

And I think you massively oversimplify the situation, to top it
off.

On the wireless front, I severely doubt... in fact I know because I'm
looking at every wireless merge going into my tree, that John Linville
is not holding back new drivers submissions from the current 2.6.26
tree.  Neither is Jeff Garzik for non-wireless net drivers.

If the Fedora9 tree is based off of 2.6.25 or similar (it is), well
that's how life works.  Stuff gets backported from mainline into
whatever they are using and stuff breaks from time to time.

Did you investigate any of these facts to figure out what the specific
situation is here?  Or did some of your favorite keywords pop up Arjan's
report so that you could unleash your favorite whine?
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ