Re: [Devel] [PATCH rh7] net: nf_synproxy: Direct conntrack allocation

2016-09-16 Thread Andrei Vagin
On Thu, Sep 15, 2016 at 06:35:42PM +0300, Kirill Tkhai wrote: > Since synproxy conntrack allow_conntrack_allocation() is executed > from pernet init, loading nf_synproxy_core() module allows conntracks > for all nets. > > Fix that by direct allocation of synproxy sample conntrack (and do not > all

[Devel] [PATCH RHEL7 COMMIT] net: nf_synproxy: Direct conntrack allocation

2016-09-16 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.28.2.vz7.17.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.28.2.vz7.17.6 --> commit 9a3d0a0422a5f5e4a8b551f8a5a9cdf9c41c6a54 Author: Kirill Tkhai Date: Fri Sep 16 17:46:56 2016 +0400 net: nf_synp

[Devel] [PATCH RHEL7 COMMIT] ms/ovl: update atime on upperovl: update atime on upper

2016-09-16 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.28.2.vz7.17.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.28.2.vz7.17.6 --> commit 72814686c2596add559bba25d551af93193b0287 Author: Maxim Patlasov Date: Fri Sep 16 18:34:33 2016 +0400 ms/ovl: up

[Devel] [PATCH RHEL7 COMMIT] fs: use original vfsmount for touch_atime

2016-09-16 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.28.2.vz7.17.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.28.2.vz7.17.6 --> commit a427c4dfb7514de4701ad5f51e4f9442a495131c Author: Maxim Patlasov Date: Fri Sep 16 18:35:14 2016 +0400 fs: use or

[Devel] [PATCH RHEL7 COMMIT] fence-watchdog: return back message printing about fencing

2016-09-16 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.28.2.vz7.17.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.28.2.vz7.17.6 --> commit c5139843dd3bde74bd1e2b1065669fe20985b8c3 Author: Pavel Tikhomirov Date: Fri Sep 16 19:08:27 2016 +0400 fence-wa

[Devel] [PATCH RH7] fence-watchdog: fix return format in dev_hard_start_xmit

2016-09-16 Thread Pavel Tikhomirov
Status goes in ret, before fix status remained -ENOMEM and was returned from dev_queue_xmit, that is not desired behaviour - we want to drop packet silently and say NETDEV_TX_OK(that it was sent). Return NULL, before the fix we were very lucky that in dev_queue_xmit, we do not get to kfree_skb_lis