Advanced thin client solution for Linux, based on Open Source. Mix Windows and Linux applications on the same desktop.

Create an account

Subscribe to LWN

Return to the Kernel page

LWN.net Weekly Edition for August 28, 2008

Fedora, Red Hat, and distributor security

LWN.net Weekly Edition for August 21, 2008

Standards, the kernel, and Postfix

In defense of Ubuntu

Printable page

Weekly edition	Kernel	Security	Distributions	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ

Kernel release status

[Posted February 5, 2003 by corbet]

The current development kernel is 2.5.59; no development kernels have been released since January 16.

Linus is back from his travels, and has merged some 300 patches (as of this writing) into his BitKeeper tree. They include some JFS updates, a number of kbuild changes (including the merge of the new modversions code), a new aic7xxx driver, an ALSA update, various network driver fixes, a number of USB updates, a big rework of the SCSI command block allocation code, and more.

The current stable kernel is 2.4.20; there have been no 2.4.21 prepatches from Marcelo in the last week.

Alan Cox has released a couple of patches, the most recent being 2.4.21-pre4-ac2. Quite a bit of IDE work has been going on, and this patch should be handled carefully. (Indeed, there have been some reports of IDE-related deadlocks with the -ac2 patch).

(Log in to post comments)

4 KB kernel thread stack patch?

Posted Feb 6, 2003 17:57 UTC (Thu) by cpeterso (guest, #305) [Link]

Does anyone know what happened to the patch to reduce kernel thread stack size from 2 pages (8 KB) to 1 page (4 KB)? The patch was highlighted here on LWN weeks ago, but I never found any more information about whether it was merged, required more work, or was too risky for Linux 2.6..??

4 KB kernel thread stack patch?

Posted Feb 6, 2003 20:42 UTC (Thu) by Peter (guest, #1127) [Link]

Does anyone know what happened to the patch to reduce kernel thread stack size from 2 pages (8 KB) to 1 page (4 KB)? The patch was highlighted here on LWN weeks ago, but I never found any more information about whether it was merged, required more work, or was too risky for Linux 2.6..??

Well, it's certainly risky for a production system - it is good mainly for development where you are trying to spot bits of code that hog the stack. I think Linus should merge it in 2.7.1, so that it can be made safe by 2.8/3.0.

I don't know what happened to the patch, by the way.