Kernel release status [LWN.net]

The current development kernel is 2.6.0-test4, which was released by Linus on August 22. This large patch includes several hundred changesets, including numerous networking fixes, a new free_netdev() method for networking drivers (see below), a new cpumask_t type for systems with more processors than bits in a long integer, a CONFIG_BROKEN option to control access to drivers known to be broken, a magic, fast new strncpy() implementation, the addition of wireless statistics to sysfs, Twofish and Serpent support for IPSec, a bunch of power management code, new sysfs attributes to control scanning of SCSI devices, a number of IDE patches, a new sysfs "attribute group" mechanism which enables the addition of attributes in a safer way and with less boilerplate code, an ALSA update, and a mind-numbing array of other fixes and updates. See the long-format changelog for the details.

As of this writing, Linus's BitKeeper tree contains only a handful of fixes. Linus is currently on vacation, so patches are not currently being merged.

The current stable kernel is 2.4.22, released by Marcelo on August 25. Marcelo is not resting, however; he has already put out 2.4.23-pre1, which includes a merge of the IP virtual server code, an LVM update, various driver updates, a possible first step toward the eventual inclusion of XFS, and a number of fixes.

(Log in to post comments)

Status of ext3 data=journal in 2.4.22 ?

Posted Aug 28, 2003 14:40 UTC (Thu) by jvotaw (subscriber, #3678) [Link]

Hi,

Does anyone happen to know what the status of the "data=journal" mount option for ext3 is in 2.4.22? Is it believed safe to use at this point?

Thanks,

-Joel

Status of ext3 data=journal in 2.4.22 ?

Posted Sep 2, 2003 23:28 UTC (Tue) by chad.netzer (subscriber, #4257) [Link]

The Changelog for 2.4.21 claims it was fixed in that release.

http://www.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.21

search for "data=journal"

Status of ext3 data=journal in 2.4.22 ?

Posted Sep 4, 2003 15:40 UTC (Thu) by jvotaw (subscriber, #3678) [Link]

Thanks for the info. I had just tracked down the answer myself and came back here to share it.

For what it's worth, my reading of the RedHat release notes says that this bug was fixed in their kernel somewhere in their 2.4.18-* series. My guess is that if you're stuck with a RedHat kernel and are running the latest 2.4.18 (or later), you're OK.

-Joel

Kernel release status

Posted Sep 4, 2003 16:27 UTC (Thu) by Baylink (subscriber, #755) [Link]

> a new cpumask_t type for systems with more processors than bits in a long integer,

So... are there really *that* many 32-bit machines with more than 32 CPU's?

Kernel release status

Posted Sep 8, 2003 21:47 UTC (Mon) by proski (subscriber, #104) [Link]

Actually, cpumask_t becomes an array, so it's also useful for systems with more than 64 64-bit processors.