Open drakedog2008 opened 11 months ago
quoted from the comment in gerrit review:
The flushOperations() cannot guarantee all NVMeMI tasks has been drained.
E.g. we have a recursive task A created by async timer.
task A will push a NVMeMi function call to worker thread.
task A has been enqueued in the immediate_exec_que of the timer but haven't been executed because the current code (nvme->flushOperations()) in currently in the io_context.
Detailed in https://gbmc-review.googlesource.com/c/dbus-sensors/+/14999/comment/d88462cb_b06e6af6/