[Devel] [PATCH hci-8.1 1/2] ve/fs: allow host to go over limit of container mount namespace

[Pavel Tikhomirov <ptikhomirov@virtuozzo.com>]

This is something that CRIU does on dump, to get access to some mounts
(under overmounts) we have to have a copy of namespace where we can try
umounting stuff which covers the path.

Together [1] + [2] lead to those mounts been accounted to ve and not
allowed to go over the limit leading to CRIU fail. Let's relax it back.

[1] commit c53e7bc5f513 ("ve/fs: take the owner of copied mounts from the
namespace, not the task")

https://virtuozzo.atlassian.net/browse/VSTOR-147661
Feature: per-ve failcounters
Fixes: b9c2e2d6ee85 ("ve/fs: count available mounts instead of used ones") [2]
Signed-off-by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
---
 fs/namespace.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/fs/namespace.c b/fs/namespace.c
index cf77c3fb98407..75cabf7763ef6 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -3367,7 +3367,8 @@ int ve_devmnt_verify(struct ve_struct *ve, dev_t dev, char *opts, bool new_mount
 
 static inline int ve_try_reserve_mount(struct ve_struct *ve)
 {
-	int ret = ve_is_super(ve) || ve->is_pseudosuper;
+	int ret = ve_is_super(ve) || ve->is_pseudosuper ||
+		  ve_is_super(get_exec_env());
 	/* Ignore limits in ve0 and pseudosuper cases, but still count. */
 	if (ret)
 		atomic_dec(&ve->mnt_avail_nr);

-- 
2.55.0

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel