Matthew Heon faae3a7065 When refreshing after a reboot, force lock allocation ...

After a reboot, when we refresh Podman's state, we retrieved the
lock from the fresh SHM instance, but we did not mark it as
allocated to prevent it being handed out to other containers and
pods.

Provide a method for marking locks as in-use, and use it when we
refresh Podman state after a reboot.

Fixes #2900

Signed-off-by: Matthew Heon <matthew.heon@pm.me>

2019-05-06 14:17:54 -04:00

..

shm

When refreshing after a reboot, force lock allocation

2019-05-06 14:17:54 -04:00

in_memory_locks.go

When refreshing after a reboot, force lock allocation

2019-05-06 14:17:54 -04:00

lock.go

When refreshing after a reboot, force lock allocation

2019-05-06 14:17:54 -04:00

shm_lock_manager_linux.go

When refreshing after a reboot, force lock allocation

2019-05-06 14:17:54 -04:00

shm_lock_manager_unsupported.go

Add initial version of renumber backend

2019-02-21 10:51:42 -05:00