Julian Elischer writes:
> > It's not clear whether the caller of M_TRAILINGSPACE()/M_LEADINGSPACE()
> > is responsible for checking for writability, or the macros themselves.
> > It seems to make more sense that the caller would be responsible...
> > why would you call M_TRAILINGSPACE() unless you wanted to write
> > something in there?
>
> M_TRAILINGSPACE is called to ask
> "How much writable room is there after hte data here?
That's the other interpretation :-)
> your patch looks better now
> I'm wouldering however if any code other than that looks at ext_size
Like I said, I did an exhaustive search. The most interesting
example is sbdrop().
You can see for yourself.. there aren't that many files:
vi `(cd /sys && find . -type f -print | xargs grep -lw ext_size)`
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
