Update the present items on the list. Drop off a few things that either are
no longer relevant or have little chance of getting addressed and thus little impact on the release.
This commit is contained in:
Scott Long
parent
2d6acbc4c9
commit
b888f82443
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=23887
1 changed files with 26 additions and 59 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY email 'freebsd-qa'>
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/5.4R/todo.sgml,v 1.6 2005/02/02 04:00:10 kensmith Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/5.4R/todo.sgml,v 1.7 2005/02/23 23:28:07 marcel Exp $">
|
||||
<!ENTITY title "FreeBSD 5.4 Open Issues">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
|
||||
|
|
@ -59,6 +59,13 @@
|
|||
<th>Description</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Update sysinstall to handle separate packages CD</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.jhb;</td>
|
||||
<td>Avoid the need for a disc1-gnome/disc1-kde as was done for 4.11</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Entropy harvesting optimizations</td>
|
||||
<td>&status.wip;</td>
|
||||
|
|
@ -71,51 +78,6 @@
|
|||
stage to be merged to 5.x until after 5.3.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ACL_MASK override of umask support in UFS</td>
|
||||
<td>&status.new;</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
|
||||
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.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>busdma in all PCI drivers</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
|
||||
exempt.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>MAC Framework Labeling and Access Control for System V IPC</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.rwatson;</td>
|
||||
<td>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.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>KAME IPSEC without the Giant Lock</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.gnn;</td>
|
||||
<td>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.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>sparc64: no serial console on fhc(4) based machines</td>
|
||||
<td>&status.wip;</td>
|
||||
|
|
@ -140,22 +102,27 @@
|
|||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Update sysinstall to handle separate packages CD</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.scottl;</td>
|
||||
<td>Avoid the need for a disc1-gnome/disc1-kde as was done for 4.11</td>
|
||||
<td>ACL_MASK override of umask support in UFS</td>
|
||||
<td>&status.new;</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
|
||||
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.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>MAC support for NFS Server</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
|
||||
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.</td>
|
||||
<td>KAME IPSEC without the Giant Lock</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.gnn;</td>
|
||||
<td>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.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue