feat(fatfs): remember by which core an FD was opened, allow to close all FDs by a certain core

untested as of right now, but we can and do now close all FDs opened by core1 in hardware_reset(). In a fatfs_detach, we close all just like before.

Whether an FD is owned by core1 is determined via the API_CALL_MAM->call_flag member, since an API call is the only way for obtain an FD at all.

added 3-Epicardium label

With this we can also pull the acls into epicardium

Looks good to me! Thanks for keeping our codebase clean.

However, I'm only a bot - so a human will still have to approve this request.

changed milestone to %v1.4

@swym, we'd like to include this in 1.4

added 21 commits

• f95322b0...76acf664 - 19 commits from branch card10:master
• e1b34bb2 - feat(fatfs): remember by which core an FD was opened, allow to close all FDs by a certain core
• e9f87b9e - bugfix: unlock in close_all

Compare with previous version

added 2 commits

• 0227a0a2 - feat(fatfs): API to dump status of FD pool
• 5d16c11c - use RTOS's current task handle to determine which core is locking the FS

Compare with previous version

added 1 commit

• 9dac4d5f - use RTOS's current task handle to determine which core is locking the FS

Compare with previous version

Otherwise LGTM but I have not tested it. @swym if you are confident it is working, I will merge

added 1 commit

• 3f5896e0 - fix includes

Compare with previous version

added 1 commit

• f86585fa - feat(fatfs): remember by which core an FD was opened, allow to close all FDs by a certain core

Compare with previous version

Looks good to me! Thanks for keeping our codebase clean.

However, I'm only a bot - so a human will still have to approve this request.

resolved all threads

merged

mentioned in commit 8c2f6b93