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: <20091015.122402.186934862.davem@davemloft.net>
Date:	Thu, 15 Oct 2009 12:24:02 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bzolnier@...il.com
Cc:	gregkh@...e.de, david@...g.hm, stefanr@...6.in-berlin.de,
	linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: removing existing working drivers via staging

From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Date: Thu, 15 Oct 2009 19:42:40 +0200

> On Thursday 15 October 2009 18:47:26 Greg KH wrote:
>> On Thu, Oct 15, 2009 at 09:39:51AM -0700, david@...g.hm wrote:
>> > however, what I think I saw proposed was to move drivers that need to be 
>> > 'cleaned up', to staging and then dropping them if they don't get cleaned.
>> 
>> What is "proposed" is the following:
>> 
>> 	- For drivers currently in the kernel tree, that the subsystem
>> 	  maintainer, for whatever reason, feels is obsolete / broken /
>> 	  needs major cleaning / wants to get rid of, can be submitted
>> 	  to the staging maintainer to be moved to the drivers/staging/
>> 	  directory.
> 
> This is insanity and opens a door for various forms of abuse.

Being a maintainer, period, give the person these kinds of "abusive"
powers.  The same thing that controls them already, will still control
them in this case with this new rule.  And that's public pressure and
the will of the larger developer community.
--
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