Page MenuHomeFreeBSD

mbuf: provide m_freemp()
ClosedPublic

Authored by glebius on Jun 3 2024, 8:12 PM.
Tags
None
Referenced Files
F102430966: D45477.diff
Tue, Nov 12, 4:29 AM
Unknown Object (File)
Fri, Nov 1, 12:35 AM
Unknown Object (File)
Fri, Nov 1, 12:35 AM
Unknown Object (File)
Fri, Nov 1, 12:35 AM
Unknown Object (File)
Fri, Nov 1, 12:20 AM
Unknown Object (File)
Wed, Oct 16, 10:36 AM
Unknown Object (File)
Mon, Oct 14, 1:12 AM
Unknown Object (File)
Oct 9 2024, 1:19 AM
Subscribers

Details

Summary

This function follows both m_nextpkt and m_next linkage freeing all mbufs.
Note that existing m_freem() follows only m_next.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jun 3 2024, 8:15 PM
sys/kern/kern_mbuf.c
1595

m_freem() lets you pass NULL, but this function does not. Is that deliberate?

sys/kern/kern_mbuf.c
1595

Yes. I believe a good code should not call free(NULL). Of course we are obliged to support free(NULL) in userland and in kernel as well as some other freeing functions, e.g. m_freem(). I will provide a comment on top of m_freemp() that it doesn't support NULL argument.

This revision was automatically updated to reflect the committed changes.