Garrett D'Amore writes: > I think the answer is no, here, because of ip_rput. There is a risk > that some badly written driver will call putnext() to pass a packet > upstream while holding a lock. Cetainly I think this can be called > while the driver is operating in interrupt context.
Holding a lock across putnext is just a programming error. How far do we have to go to protect against programming errors? (Should the stack check for freed mblks?) -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
