|
Andrew Morton发表了Linux 2.6内核*必须修正*问题列表 ver 6。该版本分为两个部分：“必须修正的bug”和“尚未完成的新特性与加速优化”。（hutuworm编译）
※必须修正的bug:
From: Andrew Morton <akpm@digeo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: must-fix, version 6
Date: Fri, 30 May 2003 16:38:21 -0700
Must-fix bugs
=============
drivers/char/
~~~~~~~~~~~~~
o TTY locking is broken.
o see FIXME in do_tty_hangup(). This causes ppp BUGs in local_bh_enable()
o Other problems: aviro, dipankar, Alan have details.
o somebody will have to document the tty driver and ldisc API
o Lack of test cases and/or stress tests is a problem. Contributions and
suggestions are sought.
o Lots of drivers are using cli/sti and are broken.
o willy: random.c is completely lockfree, and not in a good way. i had
some patches but nothing got seriously tested.
drivers/tty
~~~~~~~~~~~
o viro: we need to fix refcounting for tty_driver (oopsable race, must fix
anyway, hopefully about a week until it''''s merged) then we can do
tty/misc/upper levels of sound and hopefully upper level of USB.
USB is a place where we _really_ need to deal with dynamic allocation of
device numbers and that will bite.
drivers/block/
~~~~~~~~~~~~~~
o RAID0 dies on strangely aligned BIOs
o Need to hoist BIO-split code out of device mapper, use that.
arjan: "if we add that function, we must be sure that it can split on
not-a-page boundaries too otherwise it''''s useless for a bunch of things"
(neilb)
1/ RAID5 should work fine. It accepts any sort of bio and always
submits a 1-page bio to the underlying device, and if my
understanding is correct, every device must be able to handle a
single page bio, no matter what the alignment (which is why raid0
has a problem - it doesn''''t).
2/ RAID1 works pretty well. The only improvement needed is to define
a merge_bvec_fn function which passes the question down to lower
layers. This should be easy except for the small fact that it is
impossible :-) There is no enforced pairing between calls to
merge_bvec_fn and submit_bh, so it is possible that a hot spare
with different restrictions could get swapped in between the one
and the other and could confuse things. I suspect that can be
worked around somehow though...
Someone sent me a patch that is sorely needed - it allows you
to simply call blk_queue_stack() (or somethink like that), and it will
get your stacked limits set appropriately.
3/ I just realised that raid0 is easier than I had previously
thought. We don''''t need the completely functional bio splitting
that dm has. We only need to be able to split a bio that has just
one page as the use of merge_bvec_fn will ensure that we never get
a larger bio that we cannot handle. And splitting a bio with only
one page is a lot easier. I now have code in my tree that
implements this quite cleanly and will probably post a patch
during the week.
o ideraid hasn''''t been ported to 2.5 at all yet.
We need to understand whether the proposed BIO split code will suffice
for this.
o CD burning. There are still a few quirks to solve wrt SG_IO and ide-cd.
Jens: The basic hang has been solved (double fault in ide-cd), there still
seems to be some cases that don''''t work too well. Don''''t really have a
handle on those :/
o lmb: Last time I looked at the multipath code (2.5.50 or so) it also
looked pretty broken; I plan to port forward the changes we did on 2.4
before KS.
o loop.c: fix http://bugzilla.kernel.org/show_bug.cgi?id=192
drivers/input/
~~~~~~~~~~~~~~
o rmk: unconverted keyboard/mouse drivers (there''''s a deadline of 2.6.0
currently on these remaining in my/Linus'''' tree.)
o viro: large absence of locking.
o synaptic touchpad support
Jens Taprogge <jens.taprogge@rwth-aachen.de> is working on this.
o andi: also the input keyboard stuff still has unusably obscure config
options for standard PC hardware.
o viro: parport is nearly as bad as that and there the code is more hairy.
IMO parport is more of "figure out what API changes are needed for its
users, get them done ASAP, then fix generic layer at leisure"
drivers/misc/
~~~~~~~~~~~~~
o rmk: UCB1[23]00 drivers, currently sitting in drivers/misc in the ARM
tree. (touchscreen, audio, gpio, type device.)
These need to be moved out of drivers/misc/ and into real places
o viro: actually, misc.c has a good chance to die. With cdev-cidr that''''s
trivial.
drivers/net/
~~~~~~~~~~~~
o rmk: network drivers. ARM people like to add tonnes of #ifdefs into
these to customise them to their hardware platform (eg, chip access
methods, addresses, etc.) I cope with this by not integrating them into my
tree. The result is that many ARM platforms can''''t be built from even my
tree without extra patches. This isn''''t sane, and has bred a culture of
network drivers not being submitted. I don''''t see this changing for 2.6
though.
drivers/net/irda/
~~~~~~~~~~~~~~~~~
o dongle drivers need to be converted to sir-dev
o irport need to be converted to sir-kthread
o new drivers (irtty-sir/smsc-ircc2/donauboe) need more testing
o rmk: Refuse IrDA initialisation if sizeof(structures) is incorrect (I''''m
not sure if we still need this; I think gcc 2.95.3 on ARM shows this
problem though.)
drivers/pci/
~~~~~~~~~~~~
o alan: Some cardbus crashes the system
(bugzilla, please?)
o We have multiple drivers walking the pci device lists and also using
things like pci_find_device in unsafe ways with no refcounting. I think
we have to make pci_find_device etc refcount somewhere and add
pci_device_put as was done with networking.
http://bugzilla.kernel.org/show_bug.cgi?id=709
(gregkh will work on this)
o willy: PCI Domain support. The ''''must-fix'''' bit of this is getting sysfs
to present the right interface to userspace so we can adapt pciutils & X to
use it.
drivers/pcmcia/
~~~~~~~~~~~~~~~
o alan: Most drivers crash the system on eject randomly with timer bugs. I
think after RMK''''s stuff is in most of the pcmcia/cardbus ones go except the
locking disaster.
(rmk, brodo: in progress)
drivers/pld/
~~~~~~~~~~~~
o rmk: EPXA (ARM platform) PLD hotswap drivers (drivers/pld)
(rmk: will work out what to do here. maybe drivers/arm/)
drivers/video/
~~~~~~~~~~~~~~
o Lots of drivers don''''t compile, others do but don''''t work.
drivers/scsi/
~~~~~~~~~~~~~
o hch: large parts of the locking are hosed or not existant
(Mike Anderson, Patrick Mansfield, Badari Pulavarty)
o shost->my_devices isn''''t locked down at all
o the host list ist locked but not refcounted, mess can happen when the
spinlock is dropped
o there are lots of members of struct Scsi_Host/scsi_device/scsi_cmnd
with very unclear locking, many of them probably want to become
atomic_t''''s or bitmaps (for the 1bit bitfields).
o there''''s lots of volatile abuse in the scsi code that needs to be
thought about.
o there''''s some global variables incremented without any locks
o Convert am53c974, dpt_i2o, initio and pci2220i to DMA-mapping
o Make inia100, cpqfc, pci2000 and dc390t compile
o Convert
wd33c99 based: a2091 a3000 gpv11 mvme174 sgiwd93 53c7xx based:
amiga7xxx bvme6000 mvme16x initio am53c974 pci2000 pci2220i qla1280
sym53c8xx dc390t
To new error handling
I think the sym53c8xx could probably be pulled out of the tree because
the sym_2 replaces it. I''''m also looking at converting the qla1280.
It also might be possible to shift the 53c7xx based drivers over to
53c700 which does the new EH stuff, but I don''''t have the hardware to check
such a shift.
For the non-compiling stuff, I''''ve probably missed a few that just aren''''t
compilable on my platforms, so any updates would be welcome. Also, are
some of our non-compiling or unconverted drivers obsolete?
o rmk: I have a pending todo: I need to put the scsi error handling through
a workout on my scsi bus from hell to make sure it does the right thing and
doesn''''t get wedged.
o qlogic drivers: merge qlogicisp, feral with a view to dropping qlogicfc
and qlogicisp
o je [1] [2] [3] [4] [5] [6] [7] [8] [9] 下一页
[C语言系列]C# 和 Linux 时间戳转换 [Web开发]PHP flock文件锁介绍
[Web开发]flock() Linux下的文件锁 [电脑应用]Linux下的六个免费的虚拟主机管理系统介绍
[电脑应用]Linux数据库大比拚 [操作系统]在Windows中玩转Linux操作系统
[办公软件]在RedHat Linux 9里安装gaim0.80 [办公软件]掌握 Linux 调试技术
[办公软件]理解 Linux 配置文件 [聊天工具]Real10 & Xpdf installation on Linux Box
| 
注：本站部分文章源于互联网，版权归原作者所有！如有侵权，请原作者与本站联系，本站将立即删除！ 本站文章除特别注明外均可转载，但需注明出处！ [MinTao学以致用网] 
