Add semaphore xMqttMutex to protect mqtt->publish() and mqtt->loop() from conflicts with other concurrent threads #2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
puterboy
changed the title
puterboy
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Protecting
mqtt->publish()fixed the problem with corruption of MQTT discovery config messages #2012Protecting
mqtt->loop()seems like good practice since that could potentially conflict with another thread runningmqtt->publishNote I left
mqtt->connectunprotected since I think that is unlikely to lead to data corruption or race conditions.Similarly, I left
mqtt->begin,mqtt->disconnect,mqtt->stop,mqtt->subscribeandmqtt->willunprotected since they occur either during setup or just prior to esp restart so I think again corruption and race conditions are unlikely.Checklist: