From c2461a2cf1530053850254e283dad25f208e1323 Mon Sep 17 00:00:00 2001
From: Hiroki Sato <hrs@FreeBSD.org>
Date: Wed, 5 May 2004 21:37:41 +0000
Subject: [PATCH] Add the twe(4) stability issue and the vmspace leak as "needs
 testing" items.

---
 en/releases/4.10R/todo.sgml | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/en/releases/4.10R/todo.sgml b/en/releases/4.10R/todo.sgml
index c548f01978..b9550deca0 100644
--- a/en/releases/4.10R/todo.sgml
+++ b/en/releases/4.10R/todo.sgml
@@ -1,7 +1,7 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
 <!ENTITY base CDATA "../..">
 <!ENTITY email 'freebsd-qa'>
-<!ENTITY date "$FreeBSD$">
+<!ENTITY date "$FreeBSD: www/en/releases/4.10R/todo.sgml,v 1.1 2004/03/29 23:18:19 scottl Exp $">
 <!ENTITY local.rel "4.10">
 <!ENTITY title "FreeBSD &local.rel; Open Issues">
 <!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@@ -65,6 +65,26 @@
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
+
+	<tr>
+	  <td>twe(4) stability problem</td>
+	  <td>&status.untested;</td>
+	  <td>--</td>
+	  <td>The twe(4) driver has a stability problem
+	    when a lot of rapid sequential small file
+	    inserts into a new directory tree.  A set of patches
+	    for the problem has been committed just before 4.10-RC3.</td>
+	</tr>
+
+	<tr>
+	  <td>vmspace leak</td>
+	  <td>&status.untested;</td>
+	  <td>--</td>
+	  <td>Copying vm_exitingcnt to the new vmspace in vmspace_exec()
+	    can make it very high values and never drop to 0 and
+	    be freed.  This can cause a system crash.  A patch for the
+	    problem has been committed just before 4.10-RC3.</td>
+	</tr>
 </table>
 
     &footer;

Issue	Status	Responsible	Description
twe(4) stability problem	&status.untested;	--	The twe(4) driver has a stability problem + when a lot of rapid sequential small file + inserts into a new directory tree. A set of patches + for the problem has been committed just before 4.10-RC3.
vmspace leak	&status.untested;	--	Copying vm_exitingcnt to the new vmspace in vmspace_exec() + can make it very high values and never drop to 0 and + be freed. This can cause a system crash. A patch for the + problem has been committed just before 4.10-RC3.