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: <48DBFCDD.5090908@oracle.com>
Date:	Thu, 25 Sep 2008 14:04:29 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Greg KH <gregkh@...e.de>
CC:	Paul Mundt <lethal@...ux-sh.org>,
	Parag Warudkar <parag.lkml@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Andreas Gruenbacher <agruen@...e.de>,
	Jeff Mahoney <jeffm@...e.de>
Subject: Re: [patch 00/04] RFC: Staging tree (drivers/staging)

>> ISTM that the real problems are (a) it's easier to introduce new staging/crap
>> than it is to fix EXPERIMENTAL and (b) no one wants to try to fix EXPERIMENTAL.
> 
> The whole EXPERIMENTAL issue hasn't come up in years, I'm supprised that
> people even consider it a valid option these days.
> 
> I'm all for fixing it up, but as Paul so well described, the code I'm
> talking about is WAY worse than a mere "experimental" marking, it needs
> to be explicitly pointed out that this is not even up to that level at
> all.
> 
> And as was also pointed out, the EXPERIMENTAL marking cleanup is totally
> orthogonal to the main goal here, and that is getting code into the tree
> that is not up to our "normal" merge quality levels, in order to get a
> wider audience of users and developers working on it, and using it.
> 
> Hey, if people want me to name it TAINT_GREGKH, I can do that, I thought
> I was being nice by picking TAINT_CRAP...

I don't disagree with the CRAP name... fwiw.
I think that we have enough quality problems without adding crap.

-- 
~Randy
--
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