The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 2a160eaabf65a85402dbf277a653961240e13604
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 16:28:52 2015 +0400
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit ca1a8ad937aa7b45244776a4ebfb2e18f3a29c86
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 16:28:33 2015 +0400
Francisco,
we use pull requests instead mail list for submitting patches to userspace.
Please follow https://openvz.org/Userspace_patches
On 15:19 Fri 12 Jun , Francisco Dias wrote:
Hello devs,
https://src.openvz.org/projects/OVZ/repos/ploop/browse/lib/fsutils.c#133
This makes
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 8ad5e2a13002fb4d05879692f5ca578d32373846
Author: Kirill Tkhai ktk...@odin.com
Date: Tue Jun 16 16:11:20 2015 +0400
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 5b98da5a1ae5014d5dc0ed72bbe5b9dc816ae9a7
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 16:28:27 2015 +0400
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 64796a5a4e559059485cbb0809430e5d96aaeda6
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 16:29:04 2015 +0400
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 57420894574e45a7c1f0ed6e430566b2288e01ef
Author: Pavel Tikhomirov ptikhomi...@virtuozzo.com
Date: Tue Jun 16 16:07:02 2015 +0400
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit e388650feb976641e0ab2d62ec1c789f7facf5d9
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 16:28:46 2015 +0400
On Tue, Jun 16, 2015 at 01:55:50PM +0300, Kirill Tkhai wrote:
We can't use the same bit in _iptables_modules for different
modules. This leads to a memory leak, because it's cleared
after pernet exit method, so only one pernet exit is executed.
Found in the process of fixing:
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit dde5edb763032121c3d3e5ab4fd4d9b69ad8a4fd
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 16:28:14 2015 +0400
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit bcfe603c58a84bb7c623d3727938ea745dd60b6a
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 19:13:47 2015 +0400
В Вт, 16/06/2015 в 19:02 +0300, Vladimir Davydov пишет:
Since we want to be able to get/set current's exec_ub, when attaching a
task to a ub cgroup we change its exec_ub in a task_work (i.e. from its
own context, when it returns to userspace). This design works perfectly
well, but we have to
On Tue, Jun 16, 2015 at 06:19:44PM +0300, Kirill Tkhai wrote:
This patch brings a couple of problems. The first one is if we're setting
a ve cgroup for a forking task, it's possible the parent and the child
fall into different cgroups. For example, parent is inside CT, while
child is in ve0.
Since we want to be able to get/set current's exec_ub, when attaching a
task to a ub cgroup we change its exec_ub in a task_work (i.e. from its
own context, when it returns to userspace). This design works perfectly
well, but we have to be careful with forking tasks while currently we
are not.
Hm. How about stop_machine?
Bad idea.
___
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 944120565f7765cee3e69bf285320760da1e60ed
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 20:17:08 2015 +0400
В Вт, 16/06/2015 в 19:07 +0300, Cyrill Gorcunov пишет:
On Tue, Jun 16, 2015 at 06:19:44PM +0300, Kirill Tkhai wrote:
This patch brings a couple of problems. The first one is if we're setting
a ve cgroup for a forking task, it's possible the parent and the child
fall into different
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 73997df7ea94fc95b7b0db70fbacc1c791a89acb
Author: Vladimir Davydov vdavy...@parallels.com
Date: Tue Jun 16 19:14:09 2015 +0400
В Чт, 14/05/2015 в 19:52 +0300, Cyrill Gorcunov пишет:
In vzctl/libvzctl bundle we restore container like
- create ve/$ctid cgroup
- move self into this cgroup
- run criu from inside
So that kernel code passes ve_can_attach test. In turn for
our P.Haul project (which is managing live
On Tue, Jun 16, 2015 at 06:19:44PM +0300, Kirill Tkhai wrote:
This patch brings a couple of problems. The first one is if we're setting
a ve cgroup for a forking task, it's possible the parent and the child
fall into different cgroups. For example, parent is inside CT, while
child is in ve0.
On Tue, Jun 16, 2015 at 07:25:48PM +0300, Kirill Tkhai wrote:
May not we simply add into ve cgroup?
.can_attach
...
spin_lock(task-sighand-siglock);
.cance_attach
...
spin_unlock(task-sighand-siglock);
.attach
...
spin_unlock(task-sighand-siglock);
В Вт, 16/06/2015 в 19:36 +0300, Cyrill Gorcunov пишет:
On Tue, Jun 16, 2015 at 07:25:48PM +0300, Kirill Tkhai wrote:
May not we simply add into ve cgroup?
.can_attach
...
spin_lock(task-sighand-siglock);
.cance_attach
...
spin_unlock(task-sighand-siglock);
It was introduced initially in order to avoid the bridge's mac addr
change when a device is added/removed from the bridge. It is redundant
now, because we can force the bridge's MAC addr to a specific value, see
e.g.
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 625e4b639c0ac473bea2dc49b50b3efaa00abcf8
Author: Konstantin Khorenko khore...@virtuozzo.com
Date: Tue Jun 16 20:32:51 2015 +0400
On Tue, Jun 16, 2015 at 07:44:08PM +0300, Kirill Tkhai wrote:
We gonna move only one task in container start time so I think
this is not critical in timing.
As to #2 -- yes, I think rcu-readlock with sync should do the trick.
Also I need to check in details what Vladimir suggested,
Drop this patch - it is incomplete. Will send v2 soon.
___
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
It was introduced initially in order to avoid the bridge's mac addr
change when a device is added/removed from the bridge. It is redundant
now, because we can force the bridge's MAC addr to a specific value, see
e.g.
It is not used anywhere.
Signed-off-by: Vladimir Davydov vdavy...@parallels.com
---
include/linux/skbuff.h | 3 ---
net/core/skbuff.c | 7 ---
2 files changed, 10 deletions(-)
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index 7263f72172eb..5832e933a0f2 100644
---
The commit is pushed to branch-rh7-3.10.0-123.1.2-ovz and will appear at
https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-123.1.2.vz7.5.13
--
commit 653ecdedcbbe87b857f79a0091d77aaa5ee46ff4
Author: Konstantin Khorenko khore...@virtuozzo.com
Date: Tue Jun 16 12:15:13 2015 +0400
Hello devs,
https://src.openvz.org/projects/OVZ/repos/ploop/browse/lib/fsutils.c#133
This makes /etc/mke2fs.conf not be listened to, which causes issues
with vzctl convert and such not applying the inode_ratio a user
wants.
--- fsutils.orginal.c 2015-06-12 15:06:09.389272552 -0700
+++
We can't use the same bit in _iptables_modules for different
modules. This leads to a memory leak, because it's cleared
after pernet exit method, so only one pernet exit is executed.
Found in the process of fixing: https://jira.sw.ru/browse/PSBM-34192.
Signed-off-by: Kirill Tkhai ktk...@odin.com
move setting NETIF_F_VIRTUAL from tun_setup to tun_set_iff
where other features are set, as tun_setup is only called in
tun_set_iff
https://jira.sw.ru/browse/PSBM-34066
Signed-off-by: Pavel Tikhomirov ptikhomi...@virtuozzo.com
---
drivers/net/tun.c | 3 +--
1 file changed, 1 insertion(+), 2
In PCS6 we have a console emulation via virtual tty code
(VTTY option in config file). The code of vtty is very
close to standart pty (unix98 terminals) but on new kernels
the pty code has been heavily modified due to changes in
tty layer itself.
That said this vz console is rather a simple stub
В Вт, 16/06/2015 в 13:02 +0300, Pavel Tikhomirov пишет:
move setting NETIF_F_VIRTUAL from tun_setup to tun_set_iff
where other features are set, as tun_setup is only called in
tun_set_iff
https://jira.sw.ru/browse/PSBM-34066
Signed-off-by: Pavel Tikhomirov ptikhomi...@virtuozzo.com
34 matches
Mail list logo
