Page MenuHomeFreeBSD

mbuf: provide m_freemp()
ClosedPublic

Authored by glebius on Jun 3 2024, 8:12 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Oct 13, 4:34 PM
Unknown Object (File)
Sat, Oct 11, 12:30 AM
Unknown Object (File)
Wed, Sep 24, 6:01 PM
Unknown Object (File)
Tue, Sep 16, 10:03 AM
Unknown Object (File)
Aug 27 2025, 3:06 PM
Unknown Object (File)
Aug 15 2025, 12:50 AM
Unknown Object (File)
Jul 30 2025, 12:09 PM
Unknown Object (File)
Jul 10 2025, 10:48 PM
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.