From: de...@cerberus.ne.mediaone.net (Derek Martin)
Subject: status page?
Date: 2000/07/23
Message-ID: <Pine.LNX.4.10.10007231350050.5137-100000@sol.netria.com>#1/1
X-Deja-AN: 649829417
Sender: owner-linux-ker...@vger.rutgers.edu
X-Sender: de...@sol.netria.com
Content-Type: TEXT/PLAIN; charset=US-ASCII
MIME-Version: 1.0
Newsgroups: linux.dev.kernel
X-Loop: majord...@vger.rutgers.edu
Is there a "what's currently broken" page for the development kernel
tree? As we approach the release of 2.4, and as always happens with
impending releases of a new kernel, people are getting antsy to be able to
use some of the cool new features all you guys have been working on on
"production" or "semi-production" machines.
Which begs the question, what's currently broken, and how is it likely
to affect YOU? Also, a few months back, Linus (I believe) was quoted as
saying that the 2.4 kernel should be stable enough to officially release
approximately in August. Is that still realistic?
Note that I'm not necessarily looking for someone to write up a lengthy
post answering those questions, particularly since the answers will change
on nearly a daily basis. But if there were a web page out there where the
status could be tracked, I'd love a link to it...
Thanks!
--
---------------------------------------------------------------
Derek D. Martin | Unix/Linux Geek
d...@MissionCriticalLinux.com | de...@cerberus.ne.mediaone.net
---------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
From: a...@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: status page?
Date: 2000/07/26
Message-ID: <E13HX5Y-0000fd-00@the-village.bc.nu>
X-Deja-AN: 651109738
Content-Transfer-Encoding: 7bit
Sender: owner-linux-ker...@vger.rutgers.edu
References: <Pine.LNX.4.10.10007231350050.5137-100000@sol.netria.com>
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Newsgroups: linux.dev.kernel
X-Loop: majord...@vger.rutgers.edu
This is out of date but helpful. Dont mail me updates, find someone else to
maintain it
Should Be Fixed (Confirmation Wanted)
-------------------------------------
IDE fails on some VIA boards (eg the i-opener)
Floppy driver broken by VFS changes. Other drivers may be too
(Stuff gets called after _close now - unload race possibly too)
Fbcon races
Fix all remaining PCI code to use pci_enable_device (mostly done)
Capable Of Corrupting Your FS
-----------------------------
E820 memory setup causes crashes/corruption on some laptops[**VERY NASTY**]
Use PCI DMA by default in IDE is unsafe (must not do so on via VPx x<3)
Security
--------
Fix module remove race bug (mostly done - Al Viro)
access_process_mm oops/lockup if task->mm changes (Manfred) [user can cause deliberately]
Boot Time Failures
------------------
AHA29xx driver appears to stomp other cards (may be BIOS)
AHA27xx is broken (maybe 28xx too)
Use PCI DMA 'lost interrupt' problem with some hw [which ?]
(NEC Versa LX with PIIX tuning)
HT6560/UMC8672 ide sets up stuff too early (before region stuff can be done)
Crashes on boot on some Compaqs ? (may be fixed)
Boot hangs on a range of Dell docking stations (Latitude)
In Progress
-----------
Dcache threading (Al Viro)
Merge the network fixes (DaveM)
Finish I2O merge (Intel/Alan)
Exploitable leak in file locking (Willy)
Restore O_SYNC functionality (Stephen) - core code and ext2 done
Obvious Projects For People (well if you have the hardware..)
---------------------------
pci_socket crash on unload
DEFXX driver appears broken
NCR5380 isnt smp safe
DMFE is not SMP safe
Make syncppp use new ppp code
Fix SPX socket code
Merge the 2.2 ServeRAID driver into 2.4
Merge the current Compaq RAID driver into 2.4
Fix Exists But Isnt Merged
--------------------------
Update SGI VisWS to new-style IRQ handling (Ingo)
64bit lockf support
Support MP table above 1Gig (Ingo)
Dont panic on boot when meeting HP boxes with wacked APIC table numbering (AC)
Scheduler bugs in RT (Dimitris)
HFS is still broken
AIC7xxx doesnt work non PCI ? (Doug says OK, new version due anyway)
Fix boards with different TSC per CPU and kill TSC use on them
Floppy last block cache flush error
TB Multisound driver hasnt been updated for new isa I/O totally.
To Do
-----
mount crashes on Alpha platforms
Check all devices use resources properly
Tulip hang on rmmod/crashes sometimes
Devfs races, Sockfs (removing NULL ->i_sb stuf) (Al Viro)
Debian report that the gcc 2.95 possibly miscompiles fault.c or mm/remap.c
(Perl script available from Arjan)
Fix further NFS races (Al Viro)
Test other file systems on write
Audit all char and block drivers to ensure they are safe with the 2.3
locking - a lot of them are not especially on the open() path.
Stick lock_kernel() calls around driver with issues to hard to fix nicely
for 2.4 itself
PCMCIA/Cardbus hangs, IRQ problems. (Basically unusable - Hinds pcmcia code is reliable)_
Keyboard/mouse problems (may be fixed ?)
Fix mount failures due to copy_* user mishandling
Fix default mount behaviour to disallow repeat mounting
Check all file systems are either LFS compliant or error large files
To Do But Non Showstopper
-------------------------
Finish 64bit vfs merges (lockf64 and friends missing)
Go through as 2.4pre kicks in and figure what we should mark obsolete for
the final 2.4
Union mount (Al Viro)
Per Process rtsigio limit
iget abuse in knfsd
Some people report 2.3.x serial problems
USB hangs on APM suspend on some machines
PCMCIA crashes on unloading pci_socket
ISAPnP IRQ handling failing on SB1000 + resource handling bug
DVD-RAM is apparently not working for write currently (Rogier Wolff)
Parallel ports should set SA_SHIRQ if PCI (eg in Plip)
Devfs compiled in but not mounted causes crap for ->mnt_devname of root (Al Viro)
Compatibility Errors
--------------------
Xterm broke in 2.3.99pre6 (FIONREAD/select loop)
Probably Post 2.4
-----------------
per super block write_super needs an async flag
addres_space needs a VM pressure/flush callback (Ingo)
per file_op rw_kiovec
Drivers In 2.2 not 2.4
----------------------
To Check
--------
Check O_APPEND atomicity bug fixing is complete
Protection on isize (sct) [Al Viro mostly done]
Mikulas claims we need to fix the getblk/mark_buffer_uptodate thing for
2.3.x as well
Network block device seems broken by block device changes
VFS?VM - mmap/write deadlock (demo code seems to show lock is there)
rw sempahores on page faults (mmap_sem)
kiobuf seperate lock functions/bounce/page_address fixes
Fix routing by fwmark
Some FB drivers check the A000 area and find it busy then bomb out
rw semaphores on inodes to fix read/truncate races ? [Probably fixed]
Not all device drivers are safe now the write inode lock isnt taken on write
File locking needs checking for races
Multiwrite IDE breaks on a disk error [minor issue at best]
ACPI/APM suspend issue - IDE related stuff ?
NFS bugs are fixed
Chase reports of SMB not working
IRDA calls get random bytes before random is set up
Some AWE cards are not being found by ISAPnP ??
SHM segments not always being detached and destroyed right ?
RAM disk contents vanishing on cramfs (block change) and bforget cases
ACPI hangs on boot for some systems (Are there any cases left ?)
Fixed
-----
Incredibly slow loopback tcp bug (believed fixed about 2.3.48)
COMX series WAN now merged
VM needs rebalancing or we have a bad leak
SHM works chroot
SHM back compatibility
Intel i960 problems with I2O
Symbol clashes and other mess from _three_ copies of zlib!
PCI buffer overruns
Shared memory changes change the API breaking applications (eg gimp)
Finish softnet driver port over and cleanups
via rhine oopses under load ?
SCSI generic driver crashes controllers (need to pass PCI_DIR_UNKNOWN..)
UMSDOS fixups resync (not quite done)
Make NTFS sort of work
Any user can crash FAT fs code with ftruncate
AFFS fixups
Directory race fix for UFS
Security holes in execve()
Lan Media WAN update for 2.3
Get the Emu10K merged
Paride seems to need fixes for the block changes yet
Kernel corrupts fs and gs in some situations (Ulrich has demo code)
1.07 AMI MegaRAID
Merge 2.2.15 changes (Alan)
Get RAID 0.90 in (Ingo)
S/390 Merge
NFS DoS fix (security)
Merge the RIO driver
Fix Space.c duplicate string/write to constants
Elevator and block handling queue change errors are all sorted
Make sure all drivers return 1 from their __setup functions (Done ?)
Enhanced disk statistics
Complete vfsmount merge (Al Viro)
Merge removed-buf-open directory stuff into VFS (Al Viro)
Problems with ip autoconfig according to Zaitcev
NFS causes dup kmem_create on reload (Trond)
vmalloc(GFP_DMA) is needed for DMA drivers (Ingo)
TLB flush should use highest priority (Ingo)
SMP affinity code creates multiple dirs with the same name (Ingo)
Set SMP affinity mask to actual cpu online mask (needed for some boards) (Ingo)
heavy swapping corrupts ptes (believed so)
pci_set_master forces a 64 latency on low latency setting devices.Some
boards require all cards have latency <= 32
msync fails on NFS (probably fixed anyway)
Find out what has ruined disk I/O throughput. (mostly)
PIII FXSAVE/FXRESTORE support
The netdev name changing stuff broke GRE
put_user is broken for i386 machines (security) - sem stuff may be wrong too
BusLogic crashes when you cat /proc/scsi/BusLogic/0 (Robert de Vries)
Finish sorting out VM balancing (Rik Van Riel, Juan Quintela et al)
Fix eth= command line
8139 + bridging fails
RtSig limit handling bug
Signals leak kernel memory (security) [FIX in ac tree]
TTY and N_HDLC layer called poll_wait twice per fd and corrupt memory
ATM layer calls poll_wait twice per fd and corrupts memory
Random calls poll_wait twice per fd and corrupts memory
PCI sound calls poll_wait twice per fd and corrupts memory
sbus audio calls poll_wait twice per fd and corrupts memory
IBM MCA driver breaks on Device_Inquiry at boot
SHM code corrupts memory (Russell)
Linux sends a 1K buffer with SCSI inquiries. The ANSI-SCSI limit is 255.
Linux uses TEST_UNIT_READY to chck for device presence on a PUN/LUN. The
INQUIRY is the only valid test allowed by the spec.
truncate_inode_pages does unsafe page cache operations
Fix the ptrace code to be back compatible and add a new PTRACE call set for
getting the PIII extra registers
EPIC100 fixes
Tlan and Epic100 crash under load
Fix hpfs_unlink (Al Viro)
exec loader permissions
Locking on getcwd
Loopback fs hangs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
From: torva...@transmeta.com (Linus Torvalds)
Subject: Re: status page?
Date: 2000/07/26
Message-ID: <8lnh79$1h4$1@penguin.transmeta.com>#1/1
X-Deja-AN: 651122275
Sender: owner-linux-ker...@vger.rutgers.edu
References: <Pine.LNX.4.10.10007231350050.5137-100000@sol.netria.com> <E13HX5Y-0000fd-00@the-village.bc.nu>
Organization: Transmeta Corporation
X-Authentication-Warning: palladium.transmeta.com: mail set sender to n...@transmeta.com using -f
Newsgroups: linux.dev.kernel
X-Loop: majord...@vger.rutgers.edu
In article <E13HX5Y-0000fd...@the-village.bc.nu>,
Alan Cox <a...@lxorguk.ukuu.org.uk> wrote:
>This is out of date but helpful. Dont mail me updates, find someone else to
>maintain it
Note that this part of the status page really is worth some attention.
Alan doesn't have the time to maintain 2.4.x issues. Which means that
right nobody is really doing it. I have a kind of general "map" in my
head, but that isn't nearly good enough..
Would somebody be interested in taking this over?
Note! It's more than just maintaining a list. It's realizing what are
show-stoppers, and what are just problems that should be fixed. It's
trying to work with people in trying to get enough information to get a
good list of problems, but it's also trying to confirm that the problem
still exists or is fixed.
It's also possibly maintaining potential fixes: keeping track of who has
suggested what fix (possibly with an actual patch). Sometimes the fixes
aren't actually usable as-is due to other issues, but even when they are
not usable they can be supremely important for people who try to fix the
same thing in a acceptable manner.
It's also good if you're respected by people already, or at least think
you can work with people without making them hate you.
In short: it's important. And it's something that Alan did for both 2.0
and 2.2. Nobody can quite live up to "being Alan", but hey, if you
don't like long beards you may be just as heppy knowing that.
Anybody?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
From: ty...@MIT.EDU (Theodore Y. Ts'o)
Subject: Re: status page?
Date: 2000/07/26
Message-ID: <200007262120.RAA04589@tsx-prime.MIT.EDU>#1/1
X-Deja-AN: 651146446
Sender: owner-linux-ker...@vger.rutgers.edu
References: <8lnh79$1h4$1@penguin.transmeta.com>
Newsgroups: linux.dev.kernel
X-Loop: majord...@vger.rutgers.edu
From: torva...@transmeta.com (Linus Torvalds)
Date: 26 Jul 2000 13:20:57 -0700
>This is out of date but helpful. Dont mail me updates, find someone else to
>maintain it
Note that this part of the status page really is worth some attention.
Alan doesn't have the time to maintain 2.4.x issues. Which means that
right nobody is really doing it. I have a kind of general "map" in my
head, but that isn't nearly good enough..
Would somebody be interested in taking this over?
I'm willing to take this over.
Note that unless Alan can give me his secret of making clones of
himself, I can't necessarily read every single message on linux-kernel;
so folks will need to send me mail explicitly if they want to make sure
I'm going to read it. I'll try to skim postings on linux-kernel, but
like most kernel developers, that isn't necessarily the most reliable
way of making sure I'll read something.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
From: torva...@transmeta.com (Linus Torvalds)
Subject: Re: status page?
Date: 2000/07/27
Message-ID: <Pine.LNX.4.10.10007270900101.2851-100000@penguin.transmeta.com>#1/1
X-Deja-AN: 651457983
Sender: owner-linux-ker...@vger.rutgers.edu
References: <7ifmZBXHw-B@khms.westfalen.de>
X-Authentication-Warning: penguin.transmeta.com: torvalds owned process doing -bs
Content-Type: TEXT/PLAIN; charset=US-ASCII
MIME-Version: 1.0
Newsgroups: linux.dev.kernel
X-Loop: majord...@vger.rutgers.edu
On 27 Jul 2000, Kai Henningsen wrote:
>
> Having an URL to check would be very nice. Also, this could go into the
> various FAQs and kernel web pages that already exist.
A number of people have suggested to me that using one of the automated
bug-tracking systems would be nice.
I don't like using them myself, but some people do. Whoever would be the
maintainer (and hey, Ted has been around since pretty much the beginning
of Linux, so I'd certainly be inclined to trust him) would make his own
choice on _how_ he does it. A web-interface sounds like a good idea. It
boils down to how much work/help it is, and personal taste of the
developer in question.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
|