fjpanag commented on PR #9064: URL: https://github.com/apache/nuttx/pull/9064#issuecomment-1520701107
Indeed, the sequence is exactly as stated above. I added a delay in stm32_eth.c line 2058 (and several prints). This causes the worker (`stm32_txtimeout_work`) to start execution before the unlocking of the network. There was no issue at all. The worker will wait, execution will return to `stm32_interrupt_work` which will properly unlock the network and return. It *could* be considered a perfomance issue (as one worker will be blocked for a few microseconds), but I don't think it is of any importance in any real-life scenario. This code will execute only in exceptional cases, and being interrupted by the new work job is very very unlikely, if not impossible. I'll just close this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
