Update TODO items from today's RE telecon.

This commit is contained in:
Bruce A. Mah 2003-04-25 19:01:35 +00:00
parent fb5fdc005c
commit 8edb06cb9d
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16685

View file

@ -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.1R/todo.sgml,v 1.14 2003/04/25 15:39:01 bmah Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.1R/todo.sgml,v 1.15 2003/04/25 16:44:34 bmah Exp $">
<!ENTITY title "FreeBSD 5.1 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -41,17 +41,6 @@
still exists.</td>
</tr>
<tr>
<td>wait4 "impossible" mutex panic</td>
<td>In progress</td>
<td>&a.tjr;</td>
<td>&a.kris; reports mutex panics in wait4 in the bento environment:
"Impossible" mutex panic in wait4() (reported to -current a while
ago). This has not recurred, but no-one could track it down. It's
suspiciously similar to the other mutex panics I've been seeing more
recently (see uidinfo "impossible" mutex panic).</td>
</tr>
<tr>
<td>SMP double fault</td>
<td>--</td>
@ -75,17 +64,6 @@
into them.</td>
</tr>
<tr>
<td>uidinfo "impossible" panic</td>
<td>In progress</td>
<td>&a.tjr;</td>
<td>&a.kris; reports that there appears to be a resource leak of
uidinfo reference counts that is causing the gohan machines to panic
after about 18 days of load. &a.tjr; has given me a patch to assert
against reference count overflow, which will hopefully trigger in
about 18 days from now.</td>
</tr>
<tr>
<td>TIMEWAIT panic for network labeled MAC policy modules</td>
<td>In progress</td>
@ -98,6 +76,32 @@
A fix is current in testing.</td>
</tr>
<tr>
<td>ipfw/ipfw2 alignment issues on alpha/sparc64</td>
<td>In progress</td>
<td>&a.luigi;</td>
<td>There are reports of alignment problems with ipfw and/or ipfw2
on 64-bit platforms (specifically alpha and sparc64).</td>
</tr>
<tr>
<td>ia64 stability</td>
<td>--</td>
<td>--</td>
<td>&a.kris; reports high instability of 5.0-CURRENT on ia64
machines, such as the pluto* machines. These problems need to be
fixed in order to get a successful package build.</td>
</tr>
<tr>
<td>gcc sparc64 problems</td>
<td>--</td>
<td>--</td>
<td>&a.kris; reports that there is a gcc bug on sparc64 that
prevents the build of XFree86-4-libraries. &a.kan; is working on
a gcc 3.3 patchset for test.</td>
</tr>
</table>
<h3>Desired Features for 5.1-RELEASE</h3>
@ -106,16 +110,6 @@
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>NSSwitch support</td>
<td>In progress</td>
<td>&a.nectar;</td>
<td>Support for pluggable directory services using NSS, including
adaptations of current directory services (local databases, NIS),
and support for new services (LDAP, Active Directory, etc).
This change has now been tested, and requires broader testing.</td>
</tr>
<tr>
<td>a.out toolchain port</td>
<td>--</td>
@ -157,8 +151,8 @@
<tr>
<td>Documentation wanted: gdbe</td>
<td>--</td>
<td>--</td>
<td>In progress</td>
<td>Lucky Green</td>
<td>5.0 includes GDBE, supporting encryption of swap and storage.
It would be nice if that was documented in the handbook.</td>
</tr>
@ -228,7 +222,7 @@
<tr>
<td>UFS2 as installation, newfs default</td>
<td>In progress</td>
<td>--</td>
<td>&a.rwatson;</td>
<td>For 5.1-RELEASE, the default file system type for newly created
file systems is UFS2 rather than UFS1. newfs(8) and sysinstall(8)
@ -237,6 +231,36 @@
vital.</td>
</tr>
<tr>
<td>wait4 "impossible" mutex panic</td>
<td>--</td>
<td>&a.tjr;</td>
<td>&a.kris; reports mutex panics in wait4 in the bento environment:
"Impossible" mutex panic in wait4() (reported to -current a while
ago). Believed to be related to (and fixed along with) uidinfo
"impossible" panic below.</td>
</tr>
<tr>
<td>uidinfo "impossible" panic</td>
<td>--</td>
<td>&a.tjr;</td>
<td>&a.kris; reports that there appears to be a resource leak of
uidinfo reference counts that is causing the gohan machines to panic
after about 18 days of load. &a.tjr; has committed a fix that is
believed to solve the problem.</td>
</tr>
<tr>
<td>NSSwitch support</td>
<td>--</td>
<td>&a.nectar;</td>
<td>Support for pluggable directory services using NSS, including
adaptations of current directory services (local databases, NIS),
and support for new services (LDAP, Active Directory, etc).
This change has been committed, and requires broader testing.</td>
</tr>
</table>
&footer;