rwatson 9532a34956 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-01 14:39:06 +00:00
2014-09-21 04:38:50 +00:00
In
2013-11-30 12:51:19 +00:00
2013-07-03 18:48:43 +00:00
2012-11-25 14:25:08 +00:00
2014-09-04 19:28:02 +00:00
2014-09-24 20:12:40 +00:00