HEADSUP! netgraph Metadata changing.
Peter Ulrich Kruppa
root at pukruppa.de
Mon Jun 7 14:11:39 GMT 2004
Sorry for topposting, but I don't know if this has got something
to do with your changes:
I am trying to rebuild my -CURRENT system now for some days and
keep receiving panic messages from ng_ppoe
panic NG_MKMESSAGE() with how=M_DONTWAIT(1)
at line 913 in file /usr/src/sys/netgraph/ng_pppoe.c
netgraph/pppoe is used by ppp to connect to my ISP .
My last working kernel was built on May 31 .
Thanks, if you know how to repair this.
On Sun, 6 Jun 2004, Julian Elischer wrote:
> If you don't know or care about netgraph metadata (e.g. packet priority)
> then this shouldn't worry you.
> We are changing the netgraph metadata facility (in which arbitrary
> metadata can be sent with a packet through processing) to use
> the mbuf TAG facility that has been imported by sam.
> Netgraph tags will use different cookies to the standard set of
> tags imported with the code, so they will live in a separate namespace,
> however they will be handled during GC and manipulation by the standard
> tag handling code (Thanks to Sam for giving us the cookie facility).
> In the checked in code there are only a couple of users of metadata, but
> there may be 3rd parties out there that use it. If so the authors should
> contact me as soon as possible to co-ordinate the changeover.
> For example the BW_MAN bandwith manager uses metadata to tag
> packets selected by its ipfw netgraph node.
> Currently the biggest user of metadata is the frame relay LMI
> node that tags LMI packets with a higher priority in order to meet
> timing constraints given by the standards.
> In addition the ng_ksocket node adds info into metadata and I suspect
> there are people using that.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
| Peter Ulrich Kruppa |
| Wuppertal |
| Germany |
More information about the freebsd-current