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-next>] [day] [month] [year] [list]
Message-Id: <200712031658.lB3Gw7ds018649@agora.fsl.cs.sunysb.edu>
Date:	Mon, 3 Dec 2007 11:58:07 -0500
From:	Erez Zadok <ezk@...sunysb.edu>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: overdue items in feature-removal-schedule

Linus, Andrew, Christoph,

There are 29 listed items in feature-removal-schedule.txt.  11 of those have
dates or kernel versions that have passed, including this one:

What:	remove EXPORT_SYMBOL(kernel_thread)
When:	August 2006

One feature (removal of sys_sysctl) is listed for September 2010: are we
really able to predict the future with this much accuracy?

When, if at all, will those future/overdue features be removed for real?
Have any of them been removed already?  It's very important to developers to
have more accurate removal schedule for planning purposes.

I think setting dates on feature removal isn't compatible with the current
model of kernel code development, b/c despite our best efforts, it's hard to
predict the precise release of the next 2.6.(x+1) kernel.  I think it's
better to change all of those dates to future kernel versions (a couple of
items do so).  When those dates were assigned, was there a specific kernel
version in mind?

Thanks,
Erez.
--
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