On the FreeRTOS forum, zugo83 reported a possible leak of network buffers.
He analysed the allocations and decallocations, and i looks like the function vNDSendNeighbourSolicitation() omits to release a network buffer.
Normally the message will be passed to vReturnEthernetFrame(), which will release it. But if that function can not be called, the buffer must be released manually by calling vReleaseNetworkBufferAndDescriptor().
Test Steps
Checklist:
[x] I have tested my changes. No regression in existing tests.
[x] I have modified and/or added unit-tests to cover the code changes in this Pull Request.
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Description
On the FreeRTOS forum, zugo83 reported a possible leak of network buffers.
He analysed the allocations and decallocations, and i looks like the function
vNDSendNeighbourSolicitation()omits to release a network buffer.Normally the message will be passed to
vReturnEthernetFrame(), which will release it. But if that function can not be called, the buffer must be released manually by callingvReleaseNetworkBufferAndDescriptor().Test Steps
Checklist:
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.