mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-06 00:45:43 +00:00
a1afa58e27
As I outlined in the design docs this is broken, there are several data races here because we write to the config files that can be read by other goroutines in parallel which violates the go memory model and thus can lead to runtime panics and undefined behavior. One could fix with a mutex but that would make the whole code base much more ugly and there is still the risk that something would access this field without the mutex held. I am not sure we have any users using this, it never worked for the storage side and since the service is a not a daemon any user could just stop and start it again to re-read the files without having to stop running containers. Signed-off-by: Paul Holzinger <pholzing@redhat.com> |
||
|---|---|---|
| .. | ||
| connection | ||
| check.go | ||
| connection.go | ||
| context.go | ||
| df.go | ||
| dial_stdio.go | ||
| events.go | ||
| info.go | ||
| locks.go | ||
| migrate.go | ||
| prune.go | ||
| renumber.go | ||
| reset.go | ||
| reset_machine.go | ||
| reset_machine_unsupported.go | ||
| service.go | ||
| service_abi.go | ||
| service_abi_common.go | ||
| service_abi_linux.go | ||
| system.go | ||
| unshare.go | ||
| version.go | ||