Mark multicast and full UFS file system problems as "done" since they've

seen adequate testing.
This commit is contained in:
Robert Watson 2005-10-11 21:11:25 +00:00
parent 1288da7eb3
commit abbfdc2bb8
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=25981

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/6.0R/todo.sgml,v 1.49 2005/10/06 15:09:30 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.50 2005/10/06 18:19:38 joel Exp $">
<!ENTITY title "FreeBSD 6.0 Open Issues">
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -334,7 +334,7 @@
<tr>
<td>Panic when filesystem fills</td>
<td>&status.untested;</td>
<td>&status.done;</td>
<td>&a.rwatson;</td>
<td>Inadequate locking causes panics when calling kernel printf functions.
This is most often seen when a filesystem fills up and uprintf() is
@ -349,7 +349,7 @@
<tr>
<td>panic on multicast socket close after interface removal</td>
<td>&status.untested;</td>
<td>&status.done;</td>
<td>&a.rwatson;</td>
<td>Due to the addition of multicast locking, a long-present memory
corruption bug now generates an immediate panic if an interface is