Standardize the format of the status fields.
This commit is contained in:
parent
ed3e9f857c
commit
7ade4dab67
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=18883
1 changed files with 38 additions and 31 deletions
|
@ -1,10 +1,17 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY email 'freebsd-qa'>
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/5.2R/todo.sgml,v 1.48 2003/11/11 07:42:53 hmp Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/5.2R/todo.sgml,v 1.49 2003/11/13 05:05:43 scottl Exp $">
|
||||
<!ENTITY title "FreeBSD 5.2 Open Issues">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
|
||||
<!-- Status levels -->
|
||||
<!ENTITY status.na "<font color=green>N/A</font>">
|
||||
<!ENTITY status.done "<font color=green>Done</font>">
|
||||
<!ENTITY status.wip "<font color=blue>In progress</font>">
|
||||
<!ENTITY status.untested "<font color=yellow>Needs testing</font>">
|
||||
<!ENTITY status.new "<font color=red>Not done</font>">
|
||||
<!ENTITY status.unknown "<font color=red>Unknown</font>">
|
||||
]>
|
||||
|
||||
<html>
|
||||
|
@ -24,14 +31,14 @@
|
|||
|
||||
<tr>
|
||||
<td>Panic when rebuilding ata-raid arrays</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>The panic reported in PR kern/58228 must be fixed.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>pipe/VM corruption on Alpha</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>&a.kris; reports that Alpha packages builds are being silently corrupted
|
||||
and suspects pipe and vm issues. This must be investigated and
|
||||
|
@ -40,7 +47,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Lingering PSE instability</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>The panic reported in PR kern/58787 is likely related to PSE problems
|
||||
and must be fixed.</td>
|
||||
|
@ -56,7 +63,7 @@
|
|||
|
||||
<tr>
|
||||
<td>KSE support for sparc64</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.jake;</td>
|
||||
<td>Kernel and userland bits are implemented but untested and known to
|
||||
be incomplete. Required for 5.2-RELEASE.</td>
|
||||
|
@ -64,7 +71,7 @@
|
|||
|
||||
<tr>
|
||||
<td>KSE support for alpha</td>
|
||||
<td>In progress.</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.marcel;</td>
|
||||
<td>Userland bits implemented, kernel bits not implemented. Required for
|
||||
5.2-RELEASE.</td>
|
||||
|
@ -72,7 +79,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Fine-grained network stack locking without Giant</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.sam;</td>
|
||||
<td>Significant parts of the network stack (especially IPv4 and
|
||||
IPv6) now have fine-grained locking of their data structures.
|
||||
|
@ -86,7 +93,7 @@
|
|||
|
||||
<tr>
|
||||
<td>MAC Framework devfs path fixes</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.rwatson;</td>
|
||||
<td>&a.green; has submitted patches to improve the consistency
|
||||
of the pathnames passed into the MAC Framework devfs labeling
|
||||
|
@ -96,7 +103,7 @@
|
|||
|
||||
<tr>
|
||||
<td>ACL_MASK override of umask support in UFS</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.rwatson;</td>
|
||||
<td>Many systems supporting POSIX.1e ACLs permit a minor violation
|
||||
to that specification, in which the ACL_MASK entry overrides the
|
||||
|
@ -115,7 +122,7 @@
|
|||
|
||||
<tr>
|
||||
<td>FAST_IPSEC and KAME compatibility</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>FAST_IPSEC currently cannot be used directly with the KAME IPv6
|
||||
implementation, requiring an additional level of IP tunnel
|
||||
|
@ -128,7 +135,7 @@
|
|||
|
||||
<tr>
|
||||
<td>KAME Synchronization</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.ume;</td>
|
||||
<td>The FreeBSD KAME IPv6 code is now substantially dated with
|
||||
respect to the KAME vendor source. The FreeBSD Project needs
|
||||
|
@ -138,7 +145,7 @@
|
|||
|
||||
<tr>
|
||||
<td>truss support for ptrace</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.robert;</td>
|
||||
<td>Almost all process debugging tools have been updated to use
|
||||
non-procfs kernel primitives, with the exception of truss(1).
|
||||
|
@ -150,7 +157,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Merge of Darwin msdosfs, other fixes</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>Apple's Darwin operating system has fairly extensive improvements
|
||||
to msdosfs and other kernel services; these fixes must be reviewed
|
||||
|
@ -159,7 +166,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Tier-1 Support for AMD64 Hammer</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.peter;, &a.obrien;</td>
|
||||
<td>Productionable support for the AMD64 platform. It currently
|
||||
meets most of the requirements for the Tier-1 classification,
|
||||
|
@ -168,7 +175,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Revised kld build infrastructure</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>Kernel modules are currently built independently from a kernel
|
||||
configuration, and independently from one another, resulting in
|
||||
|
@ -184,7 +191,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Light-weight interrupt threads, context switches</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>Currently, there are two classes of interrupt handlers in 5.x:
|
||||
fast interrupt handlers which run entirely in interrupt context,
|
||||
|
@ -204,7 +211,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Run-time autoconfiguration of GBDE and related transforms</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>Currently, gbde must be manually configured at run-time each
|
||||
time an encrypted disk device is mounted. This prevents easy
|
||||
|
@ -215,7 +222,7 @@
|
|||
|
||||
<tr>
|
||||
<td>rpc.lockd(8) stability</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.rwatson;</td>
|
||||
<td>A process cannot be interrupted while waiting on a lock. Fixing
|
||||
this requires that the RPC code be taught how to deal with lock
|
||||
|
@ -239,14 +246,14 @@
|
|||
|
||||
<tr>
|
||||
<td>gdb -k support for alpha</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>&a.mp;</td>
|
||||
<td>gdb -k doesn't work on alpha</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>MAC support for NFS Server</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>&a.rwatson;</td>
|
||||
<td>Currently, MAC protections are enforced only on locally originated
|
||||
file system operations (VOPs), and not on RPCs generated via the
|
||||
|
@ -258,7 +265,7 @@
|
|||
|
||||
<tr>
|
||||
<td>busdma in all PCI drivers</td>
|
||||
<td>--</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>--</td>
|
||||
<td>All PCI drivers must use busdma for DMA; no use of vtophys() will
|
||||
be permitted for any recent device driver. ISA drivers may be
|
||||
|
@ -267,7 +274,7 @@
|
|||
|
||||
<tr>
|
||||
<td>GDB thread support</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>With improved support for threading primitives, support is now
|
||||
required to ease debugging of threaded applications. Ideally,
|
||||
|
@ -277,7 +284,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Per object ELF Prebinding support</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.mdodd;</td>
|
||||
<td><p>Prebinding reduces executable startup time by lowering the
|
||||
expense of symbol lookup, binding and relocation. This is
|
||||
|
@ -294,7 +301,7 @@
|
|||
|
||||
<tr>
|
||||
<td>filedesc LOR</td>
|
||||
<td>--</td>
|
||||
<td>&status.new;</td>
|
||||
<td>--</td>
|
||||
<td>The LOR reported in PR kern/55175 needs to be fixed. Filedesc locking
|
||||
needs to be heavily reviewed in general.</td>
|
||||
|
@ -318,7 +325,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Revise EAG</td>
|
||||
<td>--</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.bmah;</td>
|
||||
<td>The Early Adopters Guide needs to be revised, hopefully for
|
||||
the last time, to reflect the state of 5.2.</td>
|
||||
|
@ -326,7 +333,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Trim Hardware Notes</td>
|
||||
<td>In progress</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.bmah;</td>
|
||||
<td>Ongoing project to remove redundancy in documentation by
|
||||
removing lists of specific devices from the hardware notes and
|
||||
|
@ -343,7 +350,7 @@
|
|||
|
||||
<tr>
|
||||
<td>PCM locking and performance issues</td>
|
||||
<td>Complete</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>--</td>
|
||||
<td>The PCM audio framework and device drivers have been locked and
|
||||
free of Giant for quite a while, but LOR problems persist along with
|
||||
|
@ -353,7 +360,7 @@
|
|||
|
||||
<tr>
|
||||
<td>ATA driver structural improvements, MPsafety</td>
|
||||
<td>Complete</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>&a.sos;</td>
|
||||
<td>New ATA model has arrived, supporting fine-grained locking,
|
||||
and more. Much testing is needed to ensure no regressions.</td>
|
||||
|
@ -361,7 +368,7 @@
|
|||
|
||||
<tr>
|
||||
<td>GPT support for sysinstall</td>
|
||||
<td>Complete</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>&a.marcel;</td>
|
||||
<td>Sysinstall and libdisk has been overhauled to support the GPT
|
||||
partition scheme used on ia64.</td>
|
||||
|
@ -369,7 +376,7 @@
|
|||
|
||||
<tr>
|
||||
<td>Complete the APIC PCI interrupt routing support</td>
|
||||
<td>Complete</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>&a.jhb</td>
|
||||
<td>Interrupt routing on ia32 has been completely re-written to support
|
||||
ACPI hints for PCI interrupt routing, along with ACPI hints for CPU
|
||||
|
@ -378,7 +385,7 @@
|
|||
|
||||
<tr>
|
||||
<td>ATAng crashdump causes disk corruption</td>
|
||||
<td>Complete</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>&a.sos;, &a.tegge;</td>
|
||||
<td>Performing a crashdump on an ATA device can result in a corrupted
|
||||
MBR record. Tor has a possible patch for this.</td>
|
||||
|
|
Loading…
Reference in a new issue