One of the important steps in getting a 2.6.0 release out the door is
creating an organized list of crucial outstanding issues. For this
development cycle, that job seems to have fallen to Andrew Morton, who has
posted the first version
of a "must-fix"
list for 2.6.0. It's a long list, even though it does not include routine
bugs kept in the kernel bugzilla
Many of the outstanding issues can be found in the block I/O subsystem -
not surprising, considering how much things have changed there. RAID
(especially RAID0) still has some problems with large requests. CD burning
can still hang. IDE tagged command queueing still does not work correctly;
the solution here may be to just take it out for 2.6. Work in I/O
schedulers is still ongoing; some of the schedulers could use some
improvement, and there needs to be a mechanism for choosing between them.
The floppy driver is still bug-ridden. And the IDE subsystem still has a
long list of things that need to be fixed.
In the filesystem arena, ext3 still lacks a working data=journal
mode. ext3 also still uses the big kernel lock, with significant work
required for its removal. There are race conditions with asynchronous I/O and
truncate() which can corrupt filesystems. NFS still has a number
of outstanding issues.
Networking has a potential deadlock for UDP applications. IPSec has a
number of outstanding problems including a substandard key management
implementation, "mysterious TCP hangs," the lack of an MPLS implementation, and incomplete IPv6
In the kernel core, there are still complaints about poor interactive
response out of the new scheduler. The memory overcommit accounting is not
as accurate as it needs to be. There are still some issues with the
reverse-mapping VM (and the later object-based rmap patch) which can lead
to performance problems in some situations.
Then, there is still the 64-bit dev_t work; "...with the recent
rise of the neo-viro I'm not sure where things are at."
Power management still needs quite a bit of work. Much of the power
management core code remains to be merged, there needs to be a user-space
interface for power state transitions, and quite a bit of device support
work needs to be done. Restoration of video state appears to be
particularly tricky. There is also an effort afoot to rewrite the software
suspend code in a better way.
An issue which should not be overlooked is the large number of fixes from
the 2.4 series which have not yet made it into 2.5. Those all need to be
pulled together, ported forward, and merged.
The above is a summary; the full list is rather longer. But, then, these
lists are always long until the release gets close.
to post comments)