em were implemented. There''''s some real potential
+ for badness with these mostly-invisible processes. Something needs to be
+ added so that we can display and detect them.
+
+lib/kobject.c
+~~~~~~~~~~~~~
+
+o kobject refcounting (comments from Al Viro):
+
+ _anything_ can grab a temporary reference to kobject. IOW, if kobject is
+ embedded into something that could be freed - it _MUST_ have a destructor
+ and that destructor _MUST_ be the destructor for containing object.
+
+ Any violation of the above (and we already have a bunch of those) is a
+ user-triggerable memory corruption.
+
+ We can tolerate it for a while in 2.5 (e.g. during work on susbsystem we
+ can decide to switch to that way of handling objects and have subsystem
+ vulnerable for a while), but all such windows must be closed before 2.6 and
+ during 2.6 we can''''t open them at all.
+
mm/
~~~
o Overcommit accounting gets wrong answers
- o underestimates reclaimable slab, gives bogus failures when
- dcache&icache are large.
-
o gets confused by reclaimable-but-not-freed truncated ext3 pages.
- Lame fix exists in -mm.
-
-o Proper user level no overcommit also requires a root margin adding
-
-o There''''s a vmalloc race. David Woodhouse has a patch, but it had a
- problem. Need to revisit it.
o GFP_DMA32 (or something like that). Lots of ideas. jejb, zaitcev,
willy, arjan, wli.
o access_process_vm() doesn''''t flush right. We probably need new flushing
primitives to do this (davem?)
modules
~~~~~~~
@@ -449,110 +453,149 @@
o A couple of hundred real looking bugzilla bugs
o viro: cdev rework. Main group is pretty stable and I hope to feed it to
Linus RSN. That''''s cdev-cidr and ->i_cdev/->i_cindex stuff
Not-ready features and speedups
===============================
+Legend:
+
+PRI1: We''''re totally lame if this doesn''''t get in
+PRI2: Would be nice
+PRI3: Not very important
drivers/block/
~~~~~~~~~~~~~~
o Framework for selecting IO schedulers. This is the main one really.
Once this is in place we can drop in new schedulers any old time, no risk.
+ PRI1
+
o Anticipatory scheduler. Working OK now, still has problems with seeky
OLTP-style loads.
+ PRI1
+
o CFQ scheduler. Seems to work but Jens planning significant rework.
+ PRI2
+
o cryptoloop: jmorris: There''''s no cryptoloop in the 2.4 mainline kernel,
but I think every distro ships some version. It would probably be useful
to have crypto natively supported in 2.6, with backward compatibility for
the majority of 2.4 users.
problem: lack of a loop maintainer
+ PRI2
+
o viro: paride drivers need a big cleanup
+ PRI2
+
drivers/char/rtc/
~~~~~~~~~~~~~~~~~
-o rmk: I think we need a generic RTC driver (which is backed by real RTCs).
- Integrator-based stuff has a 32-bit 1Hz counter RTC with alarm, as has the
- SA11xx, and probably PXA. There''''s another implementation for the RiscPC
- and ARM26 stuff. I''''d rather not see 4 implementations of the RTC userspace
- API, but one common implementation so that stuff gets done in a consistent
- way.
-
- We postponed this at the beginning of 2.4 until 2.5 happened. We''''re now
- at 2.5, and I''''m about to add at least one more (the Integrator
- implementation.) This isn''''t sane imo.
+o rmk, trini: add support for alarms to the existing generic rtc driver.
+
+ PRI2
device mapper
~~~~~~~~~~~~~
o ioctl interface cleanup patch is ready (redo the structure layouts)
+ PRI1
+
o A port of the 2.4 snapshot target is in progress
+ PRI1
+
o the fs interface to dm needs to be redone. gregkh was going to work on
this. viro is interested in seeing work thus-far.
+ PRI2
+
drivers/net/wireless/
~~~~~~~~~~~~~~~~~~~~~
(Jean Tourrilhes <jt@bougret.hpl.hp.com>)
o get latest orinoco changes from David.
+ PRI1
+
o get the latest airo.c fixes from CVS. This will hopefully fix problems
people have reported on the LKML.
+ PRI1
+
o get HostAP driver in the kernel. No consolidation of the 802.11
management across driver can happen until this one is in (which is probably
2.7.X material). I think Jouni is mostly ready but didn''''t find time for
it.
+ PRI2
+
o get more wireless drivers into the kernel. The most "integrable" drivers
at this point seem the NWN driver, Pavel''''s Spectrum driver and the Atmel
driver.
+ PRI1
+
o The last two drivers mentioned above are held up by firmware issues (see
flamewar on LKML a few days ago). So maybe fixing those firmware issues
should be a requirement for 2.6.X, because we can expect more wireless
devices to need firmware upload at startup coming to market.
+ (in progress?)
+
+ PRI1
+
drivers/usb/gadget/
~~~~~~~~~~~~~~~~~~~
o rmk: SA11xx USB client/gadget code (David B has been doing some work on
this, and keeps trying to prod me, but unfortunately I haven''''t had the time
to look at his work, sorry David.)
+ PRI3
+
fs/
~~~
o ext3 lock_kernel() removal: that part works OK and is mergeable. But
we''''ll also need to make lock_journal() a spinlock, and that''''s deep surgery.
+ Patches exist in -mm.
+
+ PRI1
+
o ext3 and ext2 block allocators have serious failure modes - interleaved
allocations.
+ PRI3
+
o 32bit quota needs a lot more testing but may work now
+ PRI2
+
o Integrate Chris Mason''''s 2.4 reiserfs ordered data and data journaling
patches. They make reiserfs a lot safer.
+ Ordered: PRI2
+ data journalled: PRI3
+
o (Trond:) Yes: I''''m still working on an atomic "open()", i.e. one
where we short-circuit the usual VFS path_walk() + lookup() +
permission() + create() + .... bullsh*t...
I have several reasons for wanting to do this (all of
them related to NFS of course, but much of the reasoning applies
to *all* networked file systems).
1) The above sequence is simply not atomic on *any* networked
filesystem.
@@ -567,295 +610,427 @@
doesn''''t pass an ''''EXCLUSIVE'''' flag down to the filesystems.
4) (NFS specific?) open() has very different cache consistency
requirements when compared to most other VFS operations.
I''''d very much like for something like Peter Braam''''s ''''lookup with
intent'''' or (better yet) for a proper dentry->open() to be integrated with
path_walk()/open_namei(). I''''m still working on the latter (Peter has
already completed the lookup with intent stuff).
+ PRI2 (?)
+
+o (Chuck Lever <cel@citi.umich.edu>): NFS O_DIRECT support must be
+ completed. The best approach is to fall back to something like the 2.4 NFS
+ O_DIRECT support, which issues RPCs synchronously and uses the RPC
+ completion mechanism to wait for I/O completion.
+
+ PRI2
+
o rmk: update acorn partition parsing code - making all acorn schemes
appear in check.c so we don''''t have to duplicate the scanning of multiple
types, and adding support for eesox partitions.
+ PRI2
+
o atomic i_size patches
+ PRI1
+
o viro: cleaning up options-parsers in filesystems. (patch exists, needs
porting).
+ PRI2
+
o aio: fs IO isn''''t async at present. suparna has restart patches, they''''re
in -mm. Need to get Ben to review/comment.
+ PRI1.
kernel/
~~~~~~~
o rusty: Zippel''''s Reference count simplification. Tricky code, but cuts
about 120 lines上一页 [1] [2] [3] [4] [5] [6] [7] [8] [9] 下一页 |
