Re: kern/38791 (routing socket event header not cleared)

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR kern/38791; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: jtc%acorntoolworks.com@localhost, Michael van Elst 
<mlelstv%serpens.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, kern-bug-people%NetBSD.org@localhost, 
        netbsd-bugs%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
mlelstv%NetBSD.org@localhost
Subject: Re: kern/38791 (routing socket event header not cleared)
Date: Mon, 2 Jun 2008 16:33:05 -0400

 On Jun 2, 12:21pm, jtc%acorntoolworks.com@localhost (J.T. Conklin) wrote:
 -- Subject: Re: kern/38791 (routing socket event header not cleared)
 
 | Michael van Elst <mlelstv%serpens.de@localhost> writes:
 | > Let me clarify this: by erasing the message you erase the contents
 | > of the message that has been copied there two lines above with
 | > m_copyback().
 | >
 | > E.g. in case of RTM_IFINFO messages you overwrite the whole message
 | > with zeroes and thus break ifwatchd.
 | 
 | I see, I missed that difference between the code documented in
 | TCP/Illustrated and the NetBSD-current sources.  The original code did
 | not take the data and datalen parameters, so there was nothing to over-
 | write.  In the short term, I suggest reverting the change.  I'll take a
 | second look later this evening.
 
 I fixed it properly a couple of days ago.
 
 christos