You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Investigate if net_buf can be used in USB device stack and USB drivers.
Reason: The memory should be used more efficiently and secure. Unnecessary copying should be avoided. Support for multiple device instances should be considered.
There are many locale buffers in different places. Mostly these are only needed for temporary storage, whereby the content is often copied by the driver to another buffer again.
Worse is the situation with the standard, class and vendor request buffer. It is only used for the request over Control Pipe and also passed class drivers like hid and dfu. The buffer is usually not or little used during normal function. There is no verification that it is not written beyond the bounds of the buffer.
Investigate if net_buf can be used in USB device stack and USB drivers.
Reason: The memory should be used more efficiently and secure. Unnecessary copying should be avoided. Support for multiple device instances should be considered.
There are many locale buffers in different places. Mostly these are only needed for temporary storage, whereby the content is often copied by the driver to another buffer again.
Worse is the situation with the standard, class and vendor request buffer. It is only used for the request over Control Pipe and also passed class drivers like hid and dfu. The buffer is usually not or little used during normal function. There is no verification that it is not written beyond the bounds of the buffer.
Classes already uses net_buf only:
... will be continued ...
The text was updated successfully, but these errors were encountered: