Update TODO list to reflect MFC of the multicast socket / ifnet

removal fix.  Testing required.
This commit is contained in:
Robert Watson 2005-09-29 20:58:51 +00:00
parent d8dd0b4aa5
commit 6d35740865
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=25771

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.39 2005/09/22 11:19:02 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.40 2005/09/29 18:40:44 rwatson Exp $">
<!ENTITY title "FreeBSD 6.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -56,24 +56,6 @@
<th>Description</th>
</tr>
<tr>
<td>panic on multicast socket close after interface removal</td>
<td>&status.wip;</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
removed while a multicast group is in use on the interface. This
can manifest if running routed and using vlans. A regression test
has now been committed as msocket_ifnet_remove. A short-term fix
will be to GC references to the interface in the IPv4/IPv6
multicast socket options hung off of the inpcb; a long term solution
will require determining the correct application semantics for
interface removal as relates to multicast sockets. This problem is
described in detail in PR kern/77665. A fix has now been committed
to 7-CURRENT in the CVS HEAD; it will be merged to RELENG_6 after
additional testing.</td>
</tr>
<tr>
<td>race condition in POSIX named fifos</td>
<td>&status.wip;</td>
@ -401,6 +383,23 @@
merged to RELENG_6 and is ready for wide-spread testing.</td>
</tr>
<tr>
<td>panic on multicast socket close after interface removal</td>
<td>&status.untested;</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
removed while a multicast group is in use on the interface. This
can manifest if running routed and using vlans. A regression test
has now been committed as msocket_ifnet_remove. A short-term fix
will be to GC references to the interface in the IPv4/IPv6
multicast socket options hung off of the inpcb; a long term solution
will require determining the correct application semantics for
interface removal as relates to multicast sockets. This problem is
described in detail in PR kern/77665. A fix has now been committed
to 7-CURRENT in the CVS HEAD, and merged to RELENG_6.</td>
</tr>
</table>
<h3>Stress Test Panics</h3>