The commit is pushed to "branch-rh8-4.18.0-193.6.3.vz8.4.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh8-4.18.0-193.6.3.vz8.4.7
-->
commit f8e1f0f833f17767764b2fc2c7e2e4f8cb55d95e
Author: Valeriy Vdovin
Date: Wed Jul 29 10:13:47 2020 +0300
configs: Set
The commit is pushed to "branch-rh8-4.18.0-193.6.3.vz8.4.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh8-4.18.0-193.6.3.vz8.4.7
-->
commit 6b685433bed93f3f826ff45ba91979078c00e423
Author: Vasily Averin
Date: Wed Jul 29 09:39:06 2020 +0300
net/mlx5:
fsync_thread not only makes sync(), but it also may modify data.
See in kaio_fsync_thread: kaio_resubmit() submits writes, and
this is not agreed with another points of synchronizations.
This is a problem on backup (but not only), as ploop_quiesce()
never waits for fsync_thread, and we may see
Signed-off-by: Kirill Tkhai
---
drivers/block/ploop/io_kaio.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/ploop/io_kaio.c b/drivers/block/ploop/io_kaio.c
index a60b18742dd5..c2b7e8feaedf 100644
--- a/drivers/block/ploop/io_kaio.c
+++
This relaxes uuid checks for overlay index feature. It is only possible
in case there is only one filesystem for all the work/upper/lower
directories and bare file handles from this backing filesystem are uniq.
In case we have multiple filesystems here just fall back to normal
"index=on".
This is
On 9/23/20 4:41 PM, Evgenii Shatokhin wrote:
> On 23.09.2020 15:54, Vasily Averin wrote:
>> currently root inside non-trusted network namespace can consume
>> all node's memory for ipset hashtable.
>>
>> https://jira.sw.ru/browse/PSBM-108091
>> Signed-off-by: Vasily Averin
>> ---
>>
On 23.09.2020 15:54, Vasily Averin wrote:
currently root inside non-trusted network namespace can consume
all node's memory for ipset hashtable.
https://jira.sw.ru/browse/PSBM-108091
Signed-off-by: Vasily Averin
---
net/netfilter/ipset/ip_set_core.c | 4 ++--
1 file changed, 2
The commit is pushed to "branch-rh7-3.10.0-1127.18.2.vz7.163.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-1127.18.2.vz7.163.28
-->
commit 1a3cd07a8bcd508ee6c02450bfcde8780d99b7e8
Author: Valeriy Vdovin
Date: Wed Sep 23 15:57:10 2020 +0300
The commit is pushed to "branch-rh7-3.10.0-1127.18.2.vz7.163.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-1127.18.2.vz7.163.28
-->
commit 545507995ca12b24a7d1fd886a6c82b28bb47e2c
Author: Andrey Ryabinin
Date: Wed Sep 23 15:56:08 2020 +0300
mm,
The commit is pushed to "branch-rh7-3.10.0-1127.18.2.vz7.163.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-1127.18.2.vz7.163.28
-->
commit b85b3e0c99926241ad2fe32d51694b6c7405f493
Author: Vasily Averin
Date: Wed Sep 23 15:55:48 2020 +0300
The commit is pushed to "branch-rh7-3.10.0-1127.18.2.vz7.163.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-1127.18.2.vz7.163.28
-->
commit a0e271fd8929312b1c5dab72fbc8bc336a296b45
Author: Andrey Ryabinin
Date: Wed Sep 23 15:55:59 2020 +0300
currently root inside non-trusted network namespace can consume
all node's memory for ipset hashtable.
https://jira.sw.ru/browse/PSBM-108091
Signed-off-by: Vasily Averin
---
net/netfilter/ipset/ip_set_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
key->payload.data could be NULL
BUG: unable to handle kernel NULL pointer dereference at 0010
IP: user_destroy+0x13/0x30
Call Trace:
key_gc_unused_keys.constprop.1+0xfd/0x110
key_garbage_collector+0x1d7/0x390
process_one_work+0x185/0x440
worker_thread+0x126/0x3c0
Hi All,
Is /vz on nfs still supported on vz 7 as i get the following error no
matter what nfs version i use 3 or 4.1
ploop init -s 1g -t ext4 /vz/private/tst
Creating delta /vz/private/tst bs=2048 size=2097152 sectors v2
Adding snapshot {5fbaabe3-6958-40ff-92a7-860e329aab41}
Storing
14 matches
Mail list logo
