Re: 4.x mbuf binary compatibility; can it be broken?
From: Matthew Dillon (dillon_at_apollo.backplane.com)
Date: 07/15/03
- Previous message: Yar Tikhiy: "Interrupted connect(2) and errno issue"
- In reply to: Mike Silbersack: "Re: 4.x mbuf binary compatibility; can it be broken?"
- Next in thread: Matthew Dillon: "Re: 4.x mbuf binary compatibility; can it be broken?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 14 Jul 2003 21:21:19 -0700 (PDT) To: Mike Silbersack <silby@silby.com>
:> How does it get 255+ references?
:
:I don't know exactly at this point. I can reproduce the situation at will
:with (in kernel) test code, but I don't know what exactly causes it in the
:wild.
:
:Given that increasing the ref count limit is so easy, I was hoping to
:avoid spending time tracking down one degenerate case. :)
:
:Mike "Silby" Silbersack
If you just put a KASSERT() in for the 'reached 255' case the backtrace
will have a good chance of containing the likely culprit.
-Matt
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Yar Tikhiy: "Interrupted connect(2) and errno issue"
- In reply to: Mike Silbersack: "Re: 4.x mbuf binary compatibility; can it be broken?"
- Next in thread: Matthew Dillon: "Re: 4.x mbuf binary compatibility; can it be broken?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|