mirror of https://github.com/ARMmbed/mbed-os.git
cc1bad90a7
As a part of the v1.6 update, littlefs added proper handling for cleaning up memory in the case of an error during mount. This took care of a memory leak users were seeing. Ironically, it turns out the implementation and user patterns in mbed-os was _relying_ on this memory leak to avoid a double free in the same case of an error during mount. The issue was that a failed mount would leave the LittleFileSystem class in a state where it thought it was mounted, and later it would attempt to unmount the filesystem. With the previous memory leak this would be "ok", and the leaked memory would be freed. But with the fix in v1.6, no memory is leaked, and the incorrect free triggers a hard fault. Fixed to clean up state properly on failed mounts. |
||
|---|---|---|
| .. | ||
| FEATURE_BLE | ||
| FEATURE_UVISOR | ||
| TESTS/filesystem | ||
| cellular | ||
| cryptocell/FEATURE_CRYPTOCELL310 | ||
| deprecated_warnings | ||
| device_key | ||
| filesystem | ||
| frameworks | ||
| lorawan | ||
| lwipstack | ||
| mbedtls | ||
| nanostack | ||
| netsocket | ||
| nvstore | ||
| storage/FEATURE_STORAGE | ||
| unsupported | ||