fix: lock the whole markStoppendAndRelease to be automic

[allencloud]

Signed-off-by: Allen Sun allensun.shl@alibaba-inc.com

Ⅰ. Describe what this PR did

And we found that in the test case of restart, here we have a scenario that when a have ran a container, we have no idea about when the container exits. If the container exits immediately, then container would trigger the hook in pouchd, and pouchd would execute the function markStoppendAndRelease. However, if the execution time is durationA, if in this duration, pouchd accepts another request to stop or start the container, some unexpected situation would happen.

markStoppendAndRelease would excute after exit of container and release the container IO and release the container endpoint or related network items. And we must guarantee the atomic of markStoppendAndRelease.

Ⅱ. Does this pull request fix one issue?

fix #1470

Ⅲ. Describe how you did it

none

Ⅳ. Describe how to verify it

none

Ⅴ. Special notes for reviews

none

[codecov-io]

Codecov Report

Merging #1504 into master will increase coverage by 22.57%.
The diff coverage is 56.41%.

@@             Coverage Diff             @@
##           master    #1504       +/-   ##
===========================================
+ Coverage   16.88%   39.45%   +22.57%     
===========================================
  Files         211      254       +43     
  Lines       14020    17097     +3077     
===========================================
+ Hits         2367     6746     +4379     
+ Misses      11490     9482     -2008     
- Partials      163      869      +706

Impacted Files	Coverage Δ
daemon/mgr/container_state.go	77.46% <100%> (+77.46%)	⬆️
daemon/mgr/container.go	37.53% <45.16%> (+37.53%)	⬆️
client/container_logs.go	0% <0%> (-76.93%)	⬇️
pkg/utils/utils.go	57.51% <0%> (-20.85%)	⬇️
cli/logs.go	0% <0%> (ø)	⬆️
cri/stream/portforward/httpstream.go	0% <0%> (ø)
cri/stream/remotecommand/websocket.go	0% <0%> (ø)
cri/stream/remotecommand/httpstream.go	0% <0%> (ø)
cri/stream/httpstream/spdy/upgrade.go	0% <0%> (ø)
registry/auth.go	54.12% <0%> (ø)
... and 117 more

[pouchrobot]

ping @allencloud
Conflict happens after merging a previous commit.
Please rebase the branch against master and push it back again. Thanks a lot.