Move the MAC frame work and rpc.lockd items to the 5.2 list. NFS locking

appears to be working fairly well now with the exception of one issue that
can wait until 5.2 for resolution.  Also remove the kldunload and rtld
items now that they have been committed.  Thanks to imp, mux, and kan for
those!
This commit is contained in:
Scott Long 2003-05-30 17:26:11 +00:00
parent 43a06bb1e1
commit 3cf4e15dd8
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=17135
2 changed files with 23 additions and 43 deletions

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.55 2003/05/27 20:51:39 bmah Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.1R/todo.sgml,v 1.56 2003/05/29 03:17:48 rwatson Exp $">
<!ENTITY title "FreeBSD 5.1 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -39,46 +39,6 @@
fixed in order to get a successful package build.</td>
</tr>
<tr>
<td>MAC Framework devfs path fixes</td>
<td>In progress</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
entry points. These patches need to be thoroughly reviewed
and tested, then merged.</td>
</tr>
<tr>
<td>Panic on load/unload a kernel module for a driver already
statically linked into the kernel.</td>
<td>Patch approved</td>
<td>&a.mux;</td>
<td>If a network device driver, possibly any driver, is linked
into the kernel and then loaded and unloaded as a module,
the kernel will panic. This has been observed with both
if_dc and if_fxp.</td>
</tr>
<tr>
<td>rtld-elf thread-safety</td>
<td>patch submitted</td>
<td>&a.kan;</td>
<td>Update the run-time link editor (rtld) thread-safe with
libpthread.</td>
</tr>
<tr>
<td>rpc.lockd(8) stability</td>
<td>In progress</td>
<td>&a.rwatson;</td>
<td>rpc.lockd(8) client-side and server-side NFS locking appears to
have a number of serious bugs which prevent NFS locking from working
properly in a number of common scenarios. These bugs must be
resolved to ship 5.1-RELEASE. Work is underway to classify and
track the bugs.</td>
</tr>
<tr>
<td>data corruption reports</td>
<td>In progress</td>

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.2R/todo.sgml,v 1.21 2003/05/21 02:22:24 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.2R/todo.sgml,v 1.22 2003/05/27 20:03:55 scottl Exp $">
<!ENTITY title "FreeBSD 5.2 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -38,7 +38,7 @@
<td>Currently, the MD elements of KSE are present only for the i386
platform, limiting use of KSE to the i386 platform. It is highly
desirable to make KSE available on non-i386 platforms for
5.1-RELEASE so that KSE can see more broad exposure, and the
5.2-RELEASE so that KSE can see more broad exposure, and the
performance benefits of KSE can be visible to users of the
64-bit FreeBSD architectures.</td>
</tr>
@ -227,6 +227,26 @@
integration into /etc/fstab and easy automated deployment.
Improved integration with the configuration, mounting, and boot
process is required to make this feature more easily accessible.</td>
</tr>
<tr>
<td>MAC Framework devfs path fixes</td>
<td>In progress</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
entry points. These patches need to be thoroughly reviewed
and tested, then merged.</td>
</tr>
<tr>
<td>rpc.lockd(8) stability</td>
<td>In progress</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
cancellation and interruption events.</td>
</tr>
</table>