LWN.net Logo

Andrew Morton's 2.6.24 merge plans

For those who are curious about what will be merged in the next kernel development cycle: Andrew Morton has posted his 2.6.24 merge plans document. It looks like 2.6.24 will include a bunch of memory management work, more anti-fragmentation patches, per-device write throttling, the LSM non-modules patch, file-based capabilities, more memory layout randomization, control groups (formerly containers), PID namespaces, kernel markers, and much more. Remember that this list covers only patches to be merged by Andrew; the bulk of the code going into 2.6.24 will get there directly from the subsystem maintainers.
(Log in to post comments)

Obligatory ...

Posted Oct 2, 2007 5:39 UTC (Tue) by yodermk (subscriber, #3803) [Link]

> reiser4.patch

> Hold.

*Groan*

Can LWN (or someone) do a good article on the current state of affairs? Is there any hope for it? Is development still even happening?

Obligatory ...

Posted Oct 2, 2007 7:22 UTC (Tue) by engla (guest, #47454) [Link]

Is it credible that it is anywhere near? Just seeing that as one patch named "reiser4" looks like it's just one big blob of changes needing help.

Wouldn't a new filesystem to be integrated need a long series of patches? (To be clean, easy to review etc).

Obligatory ...

Posted Oct 2, 2007 7:24 UTC (Tue) by arnd (subscriber, #8866) [Link]

My understanding is that the original authors are not actively working on
this any more and no new maintainer has stepped up to fix the remaining
issues with the code base.

If someone takes responsibility for maintaining the code, it could go in,
but the chance of that happening doesn't look too good right now.
Interesting file system development is now focused on btrfs, logfs and
ext4.

Obligatory ...

Posted Oct 2, 2007 16:17 UTC (Tue) by zooko (subscriber, #2589) [Link]

Last I heard Andrew Morton said that the reiser4 hackers played well with others.

Let's see...

http://pub.namesys.com/Reiser4/ToDo

Uh-oh -- looks like it hasn't been updated in half a year.

Obligatory ...

Posted Oct 2, 2007 18:24 UTC (Tue) by zlynx (subscriber, #2285) [Link]

Edward Shishkin has been doing most of the Reiser4 work recently. However, I don't believe that any of the developers have access to the old Reiser email lists or web sites. That's one reason the email list moved to vger.kernel.org with the rest of the kernel lists.

Obligatory ...

Posted Oct 3, 2007 11:53 UTC (Wed) by intgr (subscriber, #39733) [Link]

I think the mailing list was moved because the namesys servers were being flaky and unstable. The wiki is probably unused for the same reason.

At least the FTP server is still being updated with recent patch releases: ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.23-rc1-mm1/

Obligatory ...

Posted Oct 2, 2007 13:57 UTC (Tue) by i3839 (subscriber, #31386) [Link]

The people who want Reiser4 to make it in should really lend some help achieving it. Because if the people wanting Reiser4 don't spend the effort to get there, who will?

It won't happen by itself from out of the blue you know.

Obligatory ...

Posted Oct 3, 2007 12:33 UTC (Wed) by intgr (subscriber, #39733) [Link]

If you want to stay up to date, just subscribe to reiserfs-devel@vger.kernel.org.

There has been very little development recently (as far as I can tell), but the code is still kept up to date with recent kernel releases, although with a slight lag; bugs and regressions are being fixed. This is mostly the work of Edward Shishkin, although Dave Hansen from IBM is apparently also helping.

But to get this into the kernel, the whole thing needs to be split into incremental patches which is probably going to be a significant amount of work considering how much the kernel has changed. However, the last KernelTrap article about reiser4 from April suggests that there were no major obstacles to merging reiser4 (http://kerneltrap.org/node/8102)

Andrew Morton's 2.6.24 merge plans

Posted Oct 2, 2007 18:09 UTC (Tue) by jwb (guest, #15467) [Link]

What does it mean in this list when a patch is listed as "Merge"? Does that mean these patches will be merged into the 2.6.24 mainline? Or they will appear in 2.6.24-mm?

If the write balancing for tasks is merged, that is going to be a major win for 2.6.24. I've been using it in a -mm kernel for a while and the improvement over 2.6.22 is obvious.

Andrew Morton's 2.6.24 merge plans

Posted Oct 2, 2007 19:08 UTC (Tue) by adobriyan (guest, #30858) [Link]

"Merge" roughly means "will sent to Linus for inclusion into 2.6.24". ;-)

Copyright © 2007, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds