[ovs-dev] Returned mail: Data format error

Dear user dev@openvswitch.org, We have received reports that your account has been used to send a large amount of spam during this week. We suspect that your computer was infected by a recent virus and now contains a hidden proxy server. We recommend you to follow the instructions in the attach

Re: [ovs-dev] How to setup IVSHM in OVS-DPDK

Hello Furong, Unfortunately it is not well documented, I'm going to explain what you need to start: - The ivshmem mechanism of DPDK does not work with a standard version of QEMU, then you need a patched version. It could be found at the dpdk-ovs project: https://github.com/01org/dpdk-ovs. You can

Re: [ovs-dev] [PATCH 2/2] ovsdb-client: fix memory leak reported by valgrind

On Thu, Jan 7, 2016 at 3:53 PM, William Tu wrote: > testc ase 1427: ovsdb-server combines updates on backlogged connections. > valgrind reports two leaks: > unixctl_server_create (unixctl.c:250) > do_monitor__ (ovsdb-client.c:918) > and > json_create (json.c:1406) > json_integer_c

Re: [ovs-dev] [PATCH monitor_cond 00/12] Implement conditional monitoring

On Fri, Jan 8, 2016 at 8:58 AM, Liran Schour wrote: > Andy Zhou wrote on 07/01/2016 01:04:17 AM: > > > > I have some comments on the patch series. > > > > Instead of "monitor_cond_change", why not just have a more generic > > "monitor_update" message, so we can update > > monitor columns as well

Re: [ovs-dev] [PATCH net-next v5 2/8] netfilter: Factor out nf_ct_get_info().

> On Dec 25, 2015, at 4:30 AM, Pablo Neira Ayuso wrote: > > On Wed, Dec 16, 2015 at 04:36:41PM -0800, Jarno Rajahalme wrote: >> Define a new inline function to map conntrack status to enum >> ip_conntrack_info. This removes the need to otherwise duplicate this >> code in a later patch ("openvsw

Re: [ovs-dev] [RFC] conntrack: cross zone nat

> On Jan 8, 2016, at 2:03 PM, Joe Stringer wrote: > > On 22 December 2015 at 22:05, Zang MingJie > wrote: >> >> >> On Wed, Dec 23, 2015 at 3:10 AM, Joe Stringer wrote: >>> >>> On 21 December 2015 at 23:52, Zang MingJie wrote: Hi: Problem ==

Re: [ovs-dev] [RFC] conntrack: cross zone nat

On 22 December 2015 at 22:05, Zang MingJie wrote: > > > On Wed, Dec 23, 2015 at 3:10 AM, Joe Stringer wrote: >> >> On 21 December 2015 at 23:52, Zang MingJie wrote: >> > Hi: >> > >> > Problem >> > === >> > >> > I'm glad to see that ovs add conntrack support, the conntrack support is >> > gre

Re: [ovs-dev] [PATCH net 0/2] vxlan: Set a large MTU on ovs-created vxlan devices

On 07.01.2016 19:40, Thomas Graf wrote: On 01/07/16 at 06:50pm, Hannes Frederic Sowa wrote: On 07.01.2016 18:21, Thomas Graf wrote: On 01/07/16 at 08:35am, Jesse Gross wrote: On Thu, Jan 7, 2016 at 3:49 AM, Thomas Graf wrote: A simple start could be to add a new return code for > MTU drops i

Re: [ovs-dev] [PATCH] python: Fix the TypeError exception seen when idl.Idl parses lock reply

On 01/08/2016 09:57 AM, Russell Bryant wrote: > On 01/08/2016 01:29 AM, Numan Siddique wrote: >> File "/usr/lib/python2.7/site-packages/ovs/db/idl.py", line 334, >> in __parse_lock_notify >> self.__update_has_lock(self, new_has_lock) >> TypeError: __update_has_lock() takes exactly 2 arguments (3

[ovs-dev] [PATCH net-next v6 7/7] openvswitch: Interface with NAT.

Extend OVS conntrack interface to cover NAT. New nested OVS_CT_ATTR_NAT attribute may be used to include NAT with a CT action. A bare OVS_CT_ATTR_NAT only mangles existing and expected connections. If OVS_NAT_ATTR_SRC or OVS_NAT_ATTR_DST is included within the nested attributes, new (non-committed

[ovs-dev] [PATCH net-next v6 6/7] openvswitch: Delay conntrack helper call for new connections.

There is no need to help connections that are not confirmed, so we can delay helping new connections to the time when they are confirmed. This change is needed for NAT support, and having this as a separate patch will make the following NAT patch a bit easier to review. Signed-off-by: Jarno Rajaha

[ovs-dev] [PATCH net-next v6 4/7] openvswitch: Find existing conntrack entry after upcall.

Add a new function ovs_ct_find_existing() to find an existing conntrack entry for which this packet was already applied to. This is only to be called when there is evidence that the packet was already tracked and committed, but we lost the ct reference due to an userspace upcall. ovs_ct_find_exis

[ovs-dev] [PATCH net-next v6 5/7] openvswitch: Handle NF_REPEAT in conntrack action.

Repeat the nf_conntrack_in() call when it returns NF_REPEAT. This avoids dropping a SYN packet re-opening an existing TCP connection. Signed-off-by: Jarno Rajahalme --- net/openvswitch/conntrack.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/net/openvswitch/con

[ovs-dev] [PATCH net-next v6 1/7] netfilter: Remove IP_CT_NEW_REPLY definition.

Remove the definition of IP_CT_NEW_REPLY from the kernel as it does not make sense. This allows the definition of IP_CT_NUMBER to be simplified as well. Signed-off-by: Jarno Rajahalme --- include/uapi/linux/netfilter/nf_conntrack_common.h | 12 +--- net/openvswitch/conntrack.c

[ovs-dev] [PATCH net-next v6 3/7] openvswitch: Update the CT state key only after nf_conntrack_in().

Only a successful nf_conntrack_in() call can effect a connection state change, so if suffices to update the key only after the nf_conntrack_in() returns. This change is needed for the later NAT patches. Signed-off-by: Jarno Rajahalme --- net/openvswitch/conntrack.c | 9 ++--- 1 file changed

[ovs-dev] [PATCH net-next v6 0/7] openvswitch: NAT support.

This series adds NAT support to openvswitch kernel module. A few changes are needed to the netfilter code to facilitate this (patches 1-2/8). Patches 3-6 make the openvswitch kernel module ready for the patch 7 that adds the NAT support by calling into netfilter NAT code from the openvswitch conn

[ovs-dev] [PATCH net-next v6 2/7] netfilter: Allow calling into nat helper without skb_dst.

NAT checksum recalculation code assumes existence of skb_dst, which becomes a problem for a later patch in the series ("openvswitch: Interface with NAT."). Simplify this by removing the check on skb_dst, as the checksum will be dealt with later in the stack. Suggested-by: Pravin Shelar Signed-of

Re: [ovs-dev] [PATCH] python: ignore warnings from flake8 version 2.0

On 01/08/2016 01:19 PM, Lance Richardson wrote: > Ignore warnings emitted by flake8 version 2.0 (this is the version > currently provided in the CentOS/RHEL 7 EPEL repository). > > Signed-off-by: Lance Richardson Thanks for the fix! I applied this patch to master. Since this was your first con

[ovs-dev] [PATCH] python: ignore warnings from flake8 version 2.0

Ignore warnings emitted by flake8 version 2.0 (this is the version currently provided in the CentOS/RHEL 7 EPEL repository). Signed-off-by: Lance Richardson --- Makefile.am | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index ef921ee..2537532 10

Re: [ovs-dev] [PATCH monitor_cond 00/12] Implement conditional monitoring

Andy Zhou wrote on 07/01/2016 01:04:17 AM: > > I have some comments on the patch series. > > Instead of "monitor_cond_change", why not just have a more generic > "monitor_update" message, so we can update > monitor columns as well as conditions. > In case of changing conditions, there is

Re: [ovs-dev] [PATCH v2 2/3] netdev-dpdk: Convert initialization from cmdline to db

Panu Matilainen writes: > On 01/04/2016 11:46 PM, Aaron Conole wrote: >> Existing DPDK integration is provided by use of command line options which >> must be split out and passed to librte in a special manner. However, this >> forces any configuration to be passed by way of a special DPDK flag, a

Re: [ovs-dev] [PATCH monitor_cond 11/12] python: move Python idl to work with monitor_cond

Numan Siddique wrote on 06/01/2016 03:26:22 PM: > > +elif "modify" in row_update: > +if not row: > +raise error.Error('Modify non-existing row') > + > +self.notify(ROW_UPDATE, row, > +Row.from_json(self, table, > +

Re: [ovs-dev] [PATCH] python: Fix the TypeError exception seen when idl.Idl parses lock reply

On 01/08/2016 01:29 AM, Numan Siddique wrote: > File "/usr/lib/python2.7/site-packages/ovs/db/idl.py", line 334, > in __parse_lock_notify > self.__update_has_lock(self, new_has_lock) > TypeError: __update_has_lock() takes exactly 2 arguments (3 given) > > Signed-off-by: Numan Siddique Thanks f

[ovs-dev] Get paid what you deserve get that Degree

EL0R'S, MASTER'S & DOCT0RATE DEGREES Add Bache1or's, Master's or Doctorate Degrees to your resume in just a few weeks and open avenues to promotion and better jobs! At your Own Pace! At your Own Schedule! At your Own Convenience! No Examination! No Study! No Class! Regardless of your age, sex,

Re: [ovs-dev] [PATCH] net: preserve IP control block during GSO segmentation

Hi Konstantin, [auto build test ERROR on net/master] [also build test ERROR on v4.4-rc8 next-20160108] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Konstantin-Khlebnikov/net-preserve-IP

[ovs-dev] [PATCH v2] net: preserve IP control block during GSO segmentation

Skb_gso_segment() uses skb control block during segmentation. This patch adds 32-bytes room for previous control block which will be copied into all resulting segments. This patch fixes kernel crash during fragmenting forwarded packets. Fragmentation requires valid IP CB in skb for clearing ip opt

Re: [ovs-dev] [PATCH] net: preserve IP control block during GSO segmentation

On Fri, Jan 08, 2016 at 12:13:49PM +, David Laight wrote: > From: Of Konstantin Khlebnikov > > Sent: 08 January 2016 12:01 > > Skb_gso_segment() uses skb control block during segmentation. > > This patch adds 32-bytes room for previous control block which > > will be copied into all resulting s

Re: [ovs-dev] [PATCH] net: preserve IP control block during GSO segmentation

From: Of Konstantin Khlebnikov > Sent: 08 January 2016 12:01 > Skb_gso_segment() uses skb control block during segmentation. > This patch adds 32-bytes room for previous control block which > will be copied into all resulting segments. > > This patch fixes kernel crash during fragmenting forwarded

Re: [ovs-dev] [PATCH] net: preserve IP control block during GSO segmentation

On Fri, Jan 08, 2016 at 03:00:41PM +0300, Konstantin Khlebnikov wrote: > Skb_gso_segment() uses skb control block during segmentation. > This patch adds 32-bytes room for previous control block which > will be copied into all resulting segments. > > This patch fixes kernel crash during fragmenting

Re: [ovs-dev] [PATCH] net: preserve IP control block during GSO segmentation

On Fri, Jan 8, 2016 at 3:00 PM, Konstantin Khlebnikov wrote: > Skb_gso_segment() uses skb control block during segmentation. > This patch adds 32-bytes room for previous control block which > will be copied into all resulting segments. > > This patch fixes kernel crash during fragmenting forwarded

[ovs-dev] [PATCH] net: preserve IP control block during GSO segmentation

Skb_gso_segment() uses skb control block during segmentation. This patch adds 32-bytes room for previous control block which will be copied into all resulting segments. This patch fixes kernel crash during fragmenting forwarded packets. Fragmentation requires valid IP CB in skb for clearing ip opt

[ovs-dev] Returned mail: Data format error

œm ­¢¨Eôážt9ÐŞ֢òA: ªñ…ÓÓ-yÖ6ÅK®à•óÉ3e¨—t¨ Gú H?L³!–QÍ_Ñ}2Y7%¬bØ'»’w÷(x¿ñ~\œŽÀîP³Û‚¸ý7üô‡}ZFAø›»áï—b"ÆÞ blIF¥àr~»¢7ށ%<½ð!Þ,T?t. 6Z±†`ý™dÔô' ʊM1a©†8sÕ¿ ½ûhìb)“|ċ_¸vE¼‹| ú×0â·îçŒ&“g5­†BWϑÞ#BN¥„D…‚Yªæã&‘J%’âråé †ÇULi Ž¸N, âö-&Îx˜qB«`n ’Ðê‡ðBoí¶³IetóœõD9ÉN4¸¯µ˜âÐÐPÎ흹vMQM¦Såö£ž^ˆCL±áÁ¬È4¼

[ovs-dev] Delivery reports about your e-mail

ÔÓÒ¦H%Ì0Ø´pt$(¿ºø’:˜»Í®$»“¬iiâ&ùÛ}ôgJkS͕vaG½­¢vhã~þ^-ÀÖm¤/}á}4M¯ëÎR_| <}7û]²Ež"²À—Ò{Dø½¼–ÐVÕíیϱ>$cbџ…ñ`bÛDöÄqÂ?à8Ù¼O2ׄ‡˜6•ä­fsÉÞ73&5ôíÇLÞØzU ×|)»Ü’ 0“£.ݮǻ—5eÔ?Ón·©$3!;K·¶ø£õT›Ï·à7úö >#¤ ߊ`ñҎ¹P«l¤Ù0íµ[”c~‡ù™s¤{Ä1;ûÂzdò´ÛçºgMV–nÆ_2ÛÄ\²ìHR¶ßÀ)ÈBuÑ^]3q“Çž<å:NK\­Í± aUeô(P6|¤‘–ª„-ZÀëB>é‡}ºz