diff --git a/en/releases/5.4R/todo.sgml b/en/releases/5.4R/todo.sgml index 9a61f2d335..b1ee41f20c 100644 --- a/en/releases/5.4R/todo.sgml +++ b/en/releases/5.4R/todo.sgml @@ -1,218 +1,229 @@ - + %includes; %developers; N/A"> Done"> In progress"> Needs testing"> Not done"> Unknown"> ]> &header;

Open Issues

This is the beginning of a list of open issues that need to be worked on or resolved for FreeBSD 5.4. If you have any updates for this list, please e-mail re@FreeBSD.org. The feature list for 5.4 is still a work in progress, so items may be added, removed, or modified before we're done.

Show stopper defects for 5.4-RELEASE

Issue Status Responsible Description

Required features for 5.4-RELEASE

+ + + + + +
Issue Status Responsible Description
Entropy harvesting optimizations &status.wip; &a.rwatson;, &a.markm; Entropy harvesting in the interrupt and incoming packet paths currently involves a large number of mutex operations. In order to improve performance, it is desirable to reduce the number of mutex operations substantially. Improvements in the harvesting locking scheme have been merged to 6.x, but are considered too risky at this stage to be merged to 5.x until after 5.3.
ACL_MASK override of umask support in UFS &status.new; &a.rwatson; Many systems supporting POSIX.1e ACLs permit a minor violation to that specification, in which the ACL_MASK entry overrides the umask, rather than being intersected with it. The resulting semantics can be useful in group-oriented environments, and as such would be very helpful on FreeBSD.
busdma in all PCI drivers &status.wip; -- All PCI drivers must use busdma for DMA; no use of vtophys() will be permitted for any recent device driver. ISA drivers may be exempt.
MAC Framework Labeling and Access Control for System V IPC &status.wip; &a.rwatson; Currently, the MAC Framework in the FreeBSD source tree does not provide for any additional protections of System V IPC (shm, sem, msq). The TrustedBSD MAC development branch contains labeling and access control extensions for System V IPC, and this will be merged for 5.4-RELEASE. This includes work to separate the kernel and user data structures to improve ABI resilience of the IPC implementations.
KAME IPSEC without the Giant Lock &status.wip; &a.gnn; Currently, the KAME IPSEC implementation contains inadequate locking to operate without the Giant lock over the network stack, forcing kernels compiled with the KAME IPSEC implementation (not FAST_IPSEC) to run the network stack with the Giant lock, reducing parallelism, increasing lock contention, and increasing latency by preventing preemption. For 5.4-RELEASE, it is desirable to complete the locking work for KAME IPSEC so that it can run without the Giant lock.
sparc64: no serial console on fhc(4) based machines&status.wip;&a.marcel;Now that ofw_console(4) is disabled by default on sparc64, certain + machines, like the E4x00 don't have a serial console anymore. These + machines typically have a fhc(4) bus, onto which the serial ports + attach. The fix is two-fold: 1) properly add decoding of the fhc(4) + bus addresses for low-level consoles and 2) have puc(4) attach to the + fhc(4) bus. Patches are being tested.

Desired features for 5.4-RELEASE

Issue Status Responsible Description
Update sysinstall to handle separate packages CD &status.wip; &a.scottl; Avoid the need for a disc1-gnome/disc1-kde as was done for 4.11
MAC support for NFS Server &status.new; &a.rwatson; Currently, MAC protections are enforced only on locally originated file system operations (VOPs), and not on RPCs generated via the NFS server. Improvements in NFS server credential handling are required to correct this problem, as well as the introduction of new entry points to properly label NFS credentials and perform enforcement properly.
All Network Interface Drivers MPSAFE &status.wip; -- Currently, some network interface drivers are not safe without the Giant lock due to missing synchronization. These drivers are protected by running non-INTR_MPSAFE and with the IFF_NEEDSGIANT flag set, which cause interrupt threads to acquire the Giant lock before executing the driver's interrupt handler, and to perform if_start (interface transmit start) asynchronously once the Giant lock can be acquired. This results in these drivers performing less well due to increased lock contention, decreased ability to preempt, and latency associated with asynchronous launching of latency-critical events. For 5.4, all network drivers should be able to operate without the Giant lock.
NetIPX without the Giant Lock &status.wip; &a.rwatson; Currently, the IPX/SPX (netipx) implementation contains inadequate locking to operate without the Giant lock over the network stack, forcing kernels compiled with IPX support to run the network stack with the Giant lock, reducing parallelism, increasing lock contention, and increasing latency by preventing preemption. For 5.4-RELEASE, it is desirable to complete the locking work for IPX so that it can run without the Giant lock.
Fix regression in file(1) -- -- The new version of file(1) does not cross-build properly. If sparc64 executables are built on i386 the compiled magic numbers file that gets installed is wrong and file(1) doesn't work properly.

Documentation items that must be resolved for 5.4

Issue Status Responsible Description

Testing focuses for 5.4-RELEASE

Issue Status Responsible Description
&footer;