In short, we allow concurrent existance of two ploops with same delta
image loaded in them for dmsetup reload, and we don't sync metadata in
any way to make "new" ploop have full information about what "old" ploop
left us with.
https://virtuozzo.atlassian.net/browse/VSTOR-110410
Signed-off-by: Pav
This should help finding unbalanced refcount put leading to negative
refcounts, unfreeable dst_entry-es and hanging network namespace
cleanup.
Previously we had messages like this in dmesg:
dst_release: dst:9d9686fef000 refcnt:-1
But without stack it's hard to guess the root cause.
https:
We need to provide struct pid pointer to fill_exit_event(),
so update cookie arg type of proc_event_connector() and all filler
functions to long.
https://virtuozzo.atlassian.net/browse/PSBM-161075
Signed-off-by: Konstantin Khorenko
Feature: cgroup: control group rules daemon (cgrulesengd) virtu
After do_exit() -> exit_notify() process pid and tgid may be detached
(free_pid()) before proc_exit_connector() call happens, thus
proc_exit_connector() fail to report proper pid/tgid via netlink.
Ordinary "good" scenario:
parent 37311 [000] 22305.315986: probe:alloc_pid_L85: child_process_pid=38
