[roll] Roll fuchsia [nxpfmac] Stop leaking EAPOL frame buffers

Frames used for EAPOL transmission were not correctly returned to
storage. This happened because the frames are placed in the same buffer
used for the data and after transmission they were not extracted out
correctly. This prevented the Frame object destructor from running which
in turn meant the frame would not be returned to storage. Eventually
this lead to a depletion of buffers and the driver would no longer be
able to function.

Fix this by correctly extracting the Frame object from the buffer after
transmission, allowing it to be returned on destruction.

Test: WlanSecurityComplianceABGTest ACTS tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/745989
Original-Revision: 9e5bf02839d3e556cb4b43c9fc3cc45cf4e82be7
GitOrigin-RevId: 8b7e416097d767dbcb1e46d99addae6fedc0f877
Change-Id: I329e2fd10a0425ea84ff27e0cd3b5c9533aa42c5
1 file changed
tree: f115b3ac9e6ccc91a589b8a9bcd15ecd4cfbf3f1
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.