Robert Watson f0cace5d94 When deciding whether to call m_pullup() even though there is adequate
data in an mbuf, use M_WRITABLE() instead of a direct test of M_EXT;
the latter both unnecessarily exposes mbuf-allocator internals in the
protocol stack and is also insufficient to catch all cases of
non-writability.

(NB: m_pullup() does not actually guarantee that a writable mbuf is
returned, so further refinement of all of these code paths continues to
be required.)

Reviewed by:	bz
MFC after:	3 days
Sponsored by:	EMC / Isilon Storage Division
Differential Revision: https://reviews.freebsd.org/D900
2014-10-12 15:49:52 +00:00
..
2014-10-10 14:35:51 +00:00
2014-10-10 14:35:51 +00:00
2014-10-09 07:52:51 +00:00
2014-10-09 15:19:35 +00:00
2014-10-11 20:25:19 +00:00
2014-10-11 19:36:59 +00:00
2014-10-11 16:17:49 +00:00
2014-10-11 16:34:01 +00:00
2014-10-09 19:32:35 +00:00
2014-10-09 16:12:01 +00:00
2014-10-11 15:04:50 +00:00