date:20191011

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

2019-10-11 Thread Pei, Yulong

I  had ever met this build issue with centos 7.6 before,  upgrade ninja-build 
to version 1.7.2 help me fix the issue,
Not know if it can fix your situation.

Best Regards
Yulong Pei

From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Sun, Chenmin
Sent: Saturday, October 12, 2019 9:49 AM
To: Dave Wallace ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know 
why this problem occurred, please add a suitable..." #automation

Thanks for the feedback.

Best Regards,
Sun, Chenmin

From: Dave Wallace [mailto:dwallac...@gmail.com]
Sent: Friday, October 11, 2019 11:57 PM
To: Sun, Chenmin mailto:chenmin@intel.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know 
why this problem occurred, please add a suitable..." #automation

It looks like there was some state in the build executor that didn't get 
cleaned up correctly.
I'm guessing that a new executor was used in the 'recheck' which did pass.

We'll keep an eye on this to see if it is a recurring issue.

Thanks for reporting it.
-daw-

On 10/11/2019 9:46 AM, Sun, Chenmin wrote:
Hi,
Here's my patch link. https://gerrit.fd.io/r/c/vpp/+/22637
You can see the 4th compiling passed without that error, however, I didn't 
change any code.

Best Regards,
Sun, Chenmin

From: Dave Wallace [mailto:dwallac...@gmail.com]
Sent: Friday, October 11, 2019 9:43 PM
To: Sun, Chenmin ; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know 
why this problem occurred, please add a suitable..." #automation

Please provide the link to your gerrit patch.

Thanks,
-daw-

On 10/10/2019 10:04 PM, Sun, Chenmin wrote:
Hi,
I found my patch always met an automation compiling error, stating "No problems 
were identified. If you know why this problem occurred, please add a 
suitable...".  Opening the log I can see "ninja: error: manifest 'build.ninja' 
still dirty after 100 tries". I have met 3 times on my latest patch(the 4th 
compiling is ongoing).

Does anyone know what does this error means? How to solve this problem?

-=-=-=-=-=-=-=-=-=-=-=-

Links: You receive all messages sent to this group.

View/Reply Online (#14157): https://lists.fd.io/g/vpp-dev/message/14157

Mute This Topic: https://lists.fd.io/mt/34482502/675079

Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480517

Group Owner: vpp-dev+ow...@lists.fd.io

Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[dwallac...@gmail.com]

-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14170): https://lists.fd.io/g/vpp-dev/message/14170
Mute This Topic: https://lists.fd.io/mt/34482502/21656
Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

2019-10-11 Thread Sun, Chenmin

Thanks for the feedback.

Best Regards,
Sun, Chenmin

From: Dave Wallace [mailto:dwallac...@gmail.com]
Sent: Friday, October 11, 2019 11:57 PM
To: Sun, Chenmin ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know 
why this problem occurred, please add a suitable..." #automation

It looks like there was some state in the build executor that didn't get 
cleaned up correctly.
I'm guessing that a new executor was used in the 'recheck' which did pass.

We'll keep an eye on this to see if it is a recurring issue.

Thanks for reporting it.
-daw-

On 10/11/2019 9:46 AM, Sun, Chenmin wrote:
Hi,
Here's my patch link. https://gerrit.fd.io/r/c/vpp/+/22637
You can see the 4th compiling passed without that error, however, I didn't 
change any code.

Best Regards,
Sun, Chenmin

From: Dave Wallace [mailto:dwallac...@gmail.com]
Sent: Friday, October 11, 2019 9:43 PM
To: Sun, Chenmin ; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know 
why this problem occurred, please add a suitable..." #automation

Please provide the link to your gerrit patch.

Thanks,
-daw-

On 10/10/2019 10:04 PM, Sun, Chenmin wrote:
Hi,
I found my patch always met an automation compiling error, stating "No problems 
were identified. If you know why this problem occurred, please add a 
suitable...".  Opening the log I can see "ninja: error: manifest 'build.ninja' 
still dirty after 100 tries". I have met 3 times on my latest patch(the 4th 
compiling is ongoing).

Does anyone know what does this error means? How to solve this problem?

-=-=-=-=-=-=-=-=-=-=-=-

Links: You receive all messages sent to this group.

View/Reply Online (#14157): https://lists.fd.io/g/vpp-dev/message/14157

Mute This Topic: https://lists.fd.io/mt/34482502/675079

Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480517

Group Owner: vpp-dev+ow...@lists.fd.io

Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[dwallac...@gmail.com]

-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14169): https://lists.fd.io/g/vpp-dev/message/14169
Mute This Topic: https://lists.fd.io/mt/34482502/21656
Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

2019-10-11 Thread Dave Wallace

It looks like there was some state in the build executor that didn't get 
cleaned up correctly.

I'm guessing that a new executor was used in the 'recheck' which did pass.

We'll keep an eye on this to see if it is a recurring issue.

Thanks for reporting it.
-daw-

On 10/11/2019 9:46 AM, Sun, Chenmin wrote:


Hi,

Here's my patch link. https://gerrit.fd.io/r/c/vpp/+/22637

You can see the 4th compiling passed without that error, however, I 
didn't change any code.


Best Regards,

Sun, Chenmin

*From:*Dave Wallace [mailto:dwallac...@gmail.com]
*Sent:* Friday, October 11, 2019 9:43 PM
*To:* Sun, Chenmin ; vpp-dev@lists.fd.io
*Subject:* Re: [vpp-dev] How to solve "No problems were identified. If 
you know why this problem occurred, please add a suitable..." #automation


Please provide the link to your gerrit patch.

Thanks,
-daw-

On 10/10/2019 10:04 PM, Sun, Chenmin wrote:

Hi,

I found my patch always met an automation compiling error, stating
"No problems were identified. If you know why this problem
occurred, please add a suitable...".  Opening the log I can see
"ninja: error: manifest 'build.ninja' still dirty after 100
tries". I have met 3 times on my latest patch(the 4th compiling is
ongoing).

Does anyone know what does this error means? How to solve this
problem?



-=-=-=-=-=-=-=-=-=-=-=-

Links: You receive all messages sent to this group.

View/Reply Online (#14157):https://lists.fd.io/g/vpp-dev/message/14157

Mute This Topic:https://lists.fd.io/mt/34482502/675079

Mute #automation:https://lists.fd.io/mk?hashtag=automation&subid=1480517

Group Owner:vpp-dev+ow...@lists.fd.io  

Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub   [dwallac...@gmail.com  
]

-=-=-=-=-=-=-=-=-=-=-=-



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14168): https://lists.fd.io/g/vpp-dev/message/14168
Mute This Topic: https://lists.fd.io/mt/34482502/21656
Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] tls close from cli lead to assert error

2019-10-11 Thread Florin Coras

Hi, 

First of all, that’s just a test tool that forces closing of sessions by 
“faking” a transport close request. It can potentially lead to other issues if 
afterwards the app calls the wrong apis into the transport. It shouldn’t be 
used on production traffic. 

Having said that, your problem is probably solved by this [1]. That is, we know 
the thread for the session/ctx, so we can use the explicit api. 

Florin

[1] https://gerrit.fd.io/r/c/vpp/+/22674

> On Oct 11, 2019, at 6:24 AM, jiangxiaom...@outlook.com wrote:
> 
> code: g...@github.com:FDio/vpp.git   
> master : 1a41a35b27da6921d6d86a9f1ad5f1b46e1185f7
> 
> if i close tls session which is not in thread 0, VPP will assert error.
> Below is more Info:
> 
> 
> DBGvpp# sh session verbose
> 
> ConnectionState  Rx-f  
> Tx-f  
> 
> [0:0][CT:J] 0.0.0.0:5005->0.0.0.0:0   LISTEN 0 0  
>
> 
> [0:1][TLS] app_wrk 1 engine 2 tcp 0:20 0 
> 
> [0:2][T] 0.0.0.0:5005->0.0.0.0:0  LISTEN 0 0  
>
> 
> Thread 0: active sessions 3
> 
>  
> ConnectionState  Rx-f  
> Tx-f  
> 
> [1:0][T] 192.168.7.100:5005->192.168.7.101:54206  ESTABLISHED0 0  
>
> 
> [1:1][TLS] app_wrk 1 index 0 engine 2 tcp 1:0 state: 4  0 0   
>   
> 
> Thread 1: active sessions 2
> 
> DBGvpp# clear session thread 1 session 0
> 
> 0: /home/dev/code/vpp-master/src/plugins/tlsopenssl/tls_openssl.c:72 
> (openssl_ctx_get) assertion `! pool_is_free 
> (openssl_main.ctx_pool[vlib_get_thread_index ()], _e)' fails
> 
> Program received signal SIGABRT, Aborted.
> 
> 0x74a12337 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:55
> 
> 55return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
> 
> Missing separate debuginfos, use: debuginfo-install 
> libgcc-4.8.5-39.el7.x86_64 libuuid-2.23.2-61.el7.x86_64 
> numactl-libs-2.0.12-3.el7.x86_64
> 
> (gdb) bt
> 
> #0  0x74a12337 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:55
> 
> #1  0x74a13a28 in __GI_abort () at abort.c:90
> 
> #2  0x0040765a in os_panic () at 
> /home/dev/code/vpp-master/src/vpp/vnet/main.c:355
> 
> #3  0x7585ab29 in debugger () at 
> /home/dev/code/vpp-master/src/vppinfra/error.c:84
> 
> #4  0x7585aef8 in _clib_error (how_to_die=2, function_name=0x0, 
> line_number=0, fmt=0x7fffc9a96a40 "%s:%d (%s) assertion `%s' fails") at 
> /home/dev/code/vpp-master/src/vppinfra/error.c:143
> 
> #5  0x7fffc9a9110e in openssl_ctx_get (ctx_index=0) at 
> /home/dev/code/vpp-master/src/plugins/tlsopenssl/tls_openssl.c:71
> 
> #6  0x7747f20b in tls_ctx_get (ctx_handle=1073741824) at 
> /home/dev/code/vpp-master/src/vnet/tls/tls.c:298
> 
> #7  0x7747f522 in tls_session_disconnect_callback 
> (tls_session=0x7fffdaaa54c0) at 
> /home/dev/code/vpp-master/src/vnet/tls/tls.c:389
> 
> #8  0x77445b9a in app_worker_close_notify (app_wrk=0x7fffda55d280, 
> s=0x7fffdaaa54c0) at 
> /home/dev/code/vpp-master/src/vnet/session/application_worker.c:324
> 
> #9  0x7744a45b in clear_session (s=0x7fffdaaa54c0) at 
> /home/dev/code/vpp-master/src/vnet/session/session_cli.c:594
> 
> #10 0x7744a681 in clear_session_command_fn (vm=0x766b3d80 
> , input=0x7fffda82af00, cmd=0x7fffda3ff2c0) at 
> /home/dev/code/vpp-master/src/vnet/session/session_cli.c:635
> 
> #11 0x763c5105 in vlib_cli_dispatch_sub_commands (vm=0x766b3d80 
> , cm=0x766b3fb0 , 
> input=0x7fffda82af00, parent_command_index=59) at 
> /home/dev/code/vpp-master/src/vlib/cli.c:645
> 
> #12 0x763c4f9a in vlib_cli_dispatch_sub_commands (vm=0x766b3d80 
> , cm=0x766b3fb0 , 
> input=0x7fffda82af00, parent_command_index=0) at 
> /home/dev/code/vpp-master/src/vlib/cli.c:606
> 
> #13 0x763c5530 in vlib_cli_input (vm=0x766b3d80 
> , input=0x7fffda82af00, function=0x7646b44c 
> , function_arg=0) at 
> /home/dev/code/vpp-master/src/vlib/cli.c:746
> 
> #14 0x76471626 in unix_cli_process_input (cm=0x766b4720 
> , cli_file_index=0) at 
> /home/dev/code/vpp-master/src/vlib/unix/cli.c:2572
> 
> #15 0x76472198 in unix_cli_process (vm=0x766b3d80 
> , rt=0x7fffda7ea000, f=0x0) at 
> /home/dev/code/vpp-master/src/vlib/unix/cli.c:2688
> 
> #16 0x76412884 in vlib_process_bootstrap (_a=140736833976688) at 
> /home/dev/code/vpp-master/src/vlib/main.c:1472
> 
> #17 0x7587b9a0 in clib_calljmp () from 
> /home/dev/code/vpp-master/build-root/install-vpp_debug-native/vpp/lib/libvppinfra.so.20.01
> 
> #18 0x7fffd8fef940 in ?? ()
> 
> #19 0x7641298c in vlib_process_startup (vm=0x766b3d80 
> , p=0x267, f=0x0) at 
> /home/dev/code/vpp-master/src/vlib/main.c:1494
> 
> The reason is that:
> tls_ctx_t struct is create

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

2019-10-11 Thread Sun, Chenmin

Hi,
Here's my patch link. https://gerrit.fd.io/r/c/vpp/+/22637
You can see the 4th compiling passed without that error, however, I didn't 
change any code.

Best Regards,
Sun, Chenmin

From: Dave Wallace [mailto:dwallac...@gmail.com]
Sent: Friday, October 11, 2019 9:43 PM
To: Sun, Chenmin ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know 
why this problem occurred, please add a suitable..." #automation

Please provide the link to your gerrit patch.

Thanks,
-daw-

On 10/10/2019 10:04 PM, Sun, Chenmin wrote:
Hi,
I found my patch always met an automation compiling error, stating "No problems 
were identified. If you know why this problem occurred, please add a 
suitable...".  Opening the log I can see "ninja: error: manifest 'build.ninja' 
still dirty after 100 tries". I have met 3 times on my latest patch(the 4th 
compiling is ongoing).

Does anyone know what does this error means? How to solve this problem?



-=-=-=-=-=-=-=-=-=-=-=-

Links: You receive all messages sent to this group.



View/Reply Online (#14157): https://lists.fd.io/g/vpp-dev/message/14157

Mute This Topic: https://lists.fd.io/mt/34482502/675079

Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480517

Group Owner: vpp-dev+ow...@lists.fd.io

Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[dwallac...@gmail.com]

-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14166): https://lists.fd.io/g/vpp-dev/message/14166
Mute This Topic: https://lists.fd.io/mt/34482502/21656
Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

2019-10-11 Thread Dave Wallace


Please provide the link to your gerrit patch.

Thanks,
-daw-

On 10/10/2019 10:04 PM, Sun, Chenmin wrote:

Hi,
I found my patch always met an automation compiling error, stating "No 
problems were identified. If you know why this problem occurred, 
please add a suitable...".  Opening the log I can see "ninja: error: 
manifest 'build.ninja' still dirty after 100 tries". I have met 3 
times on my latest patch(the 4th compiling is ongoing).

Does anyone know what does this error means? How to solve this problem?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14157): https://lists.fd.io/g/vpp-dev/message/14157
Mute This Topic: https://lists.fd.io/mt/34482502/675079
Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480517
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dwallac...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14165): https://lists.fd.io/g/vpp-dev/message/14165
Mute This Topic: https://lists.fd.io/mt/34482502/21656
Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] tls close from cli lead to assert error

2019-10-11 Thread jiangxiaoming

code: g...@github.com:FDio/vpp.git master : 
1a41a35b27da6921d6d86a9f1ad5f1b46e1185f7

if i close tls session which is not in thread 0, VPP will assert error.
Below is more Info:

> 
> 
> 
> DBGvpp# sh session verbose
> 
> 
> 
> Connection                                        State          Rx-f     
> Tx-f
> 
> 
> 
> [0:0][CT:J] 0.0.0.0:5005->0.0.0.0:0               LISTEN         0        
> 0
> 
> 
> 
> [0:1][TLS] app_wrk 1 engine 2 tcp 0:20         0
> 
> 
> 
> [0:2][T] 0.0.0.0:5005->0.0.0.0:0                  LISTEN         0        
> 0
> 
> 
> 
> Thread 0: active sessions 3
> 
> 
> 
> 
> 
> 
> 
> Connection                                        State          Rx-f     
> Tx-f
> 
> 
> 
> [1:0][T] 192.168.7.100:5005->192.168.7.101:54206  ESTABLISHED    0        
> 0
> 
> 
> 
> [1:1][TLS] app_wrk 1 index 0 engine 2 tcp 1:0     state: 4      0        
> 0
> 
> 
> 
> Thread 1: active sessions 2
> 
> DBGvpp# *clear session thread 1 session 0*
> 
> 0: /home/dev/code/vpp-master/src/plugins/tlsopenssl/tls_openssl.c:72
> (openssl_ctx_get) assertion `! pool_is_free
> (openssl_main.ctx_pool[vlib_get_thread_index ()], _e)' fails
> 
> 
> 
> Program received signal SIGABRT, Aborted.
> 
> 
> 
> 0x74a12337 in __GI_raise (sig=sig@entry=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:55
> 
> 
> 
> 55        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
> 
> 
> 
> Missing separate debuginfos, use: debuginfo-install
> libgcc-4.8.5-39.el7.x86_64 libuuid-2.23.2-61.el7.x86_64
> numactl-libs-2.0.12-3.el7.x86_64
> 
> 
> 
> (gdb) bt
> 
> 
> 
> #0  0x74a12337 in __GI_raise (sig=sig@entry=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:55
> 
> 
> 
> #1  0x74a13a28 in __GI_abort () at abort.c:90
> 
> 
> 
> #2  0x0040765a in os_panic () at
> /home/dev/code/vpp-master/src/vpp/vnet/main.c:355
> 
> 
> 
> #3  0x7585ab29 in debugger () at
> /home/dev/code/vpp-master/src/vppinfra/error.c:84
> 
> 
> 
> #4  0x7585aef8 in _clib_error (how_to_die=2, function_name=0x0,
> line_number=0, fmt=0x7fffc9a96a40 "%s:%d (%s) assertion `%s' fails") at
> /home/dev/code/vpp-master/src/vppinfra/error.c:143
> 
> 
> 
> #5  0x7fffc9a9110e in openssl_ctx_get (ctx_index=0) at
> /home/dev/code/vpp-master/src/plugins/tlsopenssl/tls_openssl.c:71
> 
> 
> 
> #6  0x7747f20b in tls_ctx_get (ctx_handle=1073741824) at
> /home/dev/code/vpp-master/src/vnet/tls/tls.c:298
> 
> 
> 
> #7  0x7747f522 in tls_session_disconnect_callback
> (tls_session=0x7fffdaaa54c0) at
> /home/dev/code/vpp-master/src/vnet/tls/tls.c:389
> 
> 
> 
> #8  0x77445b9a in app_worker_close_notify (app_wrk=0x7fffda55d280,
> s=0x7fffdaaa54c0) at
> /home/dev/code/vpp-master/src/vnet/session/application_worker.c:324
> 
> 
> 
> #9  0x7744a45b in clear_session (s=0x7fffdaaa54c0) at
> /home/dev/code/vpp-master/src/vnet/session/session_cli.c:594
> 
> 
> 
> #10 0x7744a681 in clear_session_command_fn (vm=0x766b3d80
> , input=0x7fffda82af00, cmd=0x7fffda3ff2c0) at
> /home/dev/code/vpp-master/src/vnet/session/session_cli.c:635
> 
> 
> 
> #11 0x763c5105 in vlib_cli_dispatch_sub_commands
> (vm=0x766b3d80 , cm=0x766b3fb0
> , input=0x7fffda82af00, parent_command_index=59) at
> /home/dev/code/vpp-master/src/vlib/cli.c:645
> 
> 
> 
> #12 0x763c4f9a in vlib_cli_dispatch_sub_commands
> (vm=0x766b3d80 , cm=0x766b3fb0
> , input=0x7fffda82af00, parent_command_index=0) at
> /home/dev/code/vpp-master/src/vlib/cli.c:606
> 
> 
> 
> #13 0x763c5530 in vlib_cli_input (vm=0x766b3d80
> , input=0x7fffda82af00, function=0x7646b44c
> , function_arg=0) at
> /home/dev/code/vpp-master/src/vlib/cli.c:746
> 
> 
> 
> #14 0x76471626 in unix_cli_process_input (cm=0x766b4720
> , cli_file_index=0) at
> /home/dev/code/vpp-master/src/vlib/unix/cli.c:2572
> 
> 
> 
> #15 0x76472198 in unix_cli_process (vm=0x766b3d80
> , rt=0x7fffda7ea000, f=0x0) at
> /home/dev/code/vpp-master/src/vlib/unix/cli.c:2688
> 
> 
> 
> #16 0x76412884 in vlib_process_bootstrap (_a=140736833976688) at
> /home/dev/code/vpp-master/src/vlib/main.c:1472
> 
> 
> 
> #17 0x7587b9a0 in clib_calljmp () from
> /home/dev/code/vpp-master/build-root/install-vpp_debug-native/vpp/lib/libvppinfra.so.20.01
> 
> 
> 
> 
> #18 0x7fffd8fef940 in ?? ()
> 
> 
> 
> #19 0x7641298c in vlib_process_startup (vm=0x766b3d80
> , p=0x267, f=0x0) at
> /home/dev/code/vpp-master/src/vlib/main.c:1494
> 
> 

The reason is that:
*tls_ctx_t* struct is create in openssl_main.ctx_pool[1], but when close form 
cli, it search from openssl_main.ctx_pool[0], and lead to crash

The ctx_index isi 32bits, and can support 4Gs ctx, but in practice we not need 
so much.
I think we can use the high 8bits for thread info, and left 24bits for pool 
index, because 4Ms ctx is already enough!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14164): https://lists.fd.io/g/vpp-de

Re: [vpp-dev] Any equivalent of "ip tcp adjust-mss" command in VPP

2019-10-11 Thread Ole Troan

Milan,

TCP MSS adjustment is supported in the NAT and MAP features. 
You should of course ensure that your endpoints support PLPMTUD instead. 

Cheers 
Ole

> On 11 Oct 2019, at 09:39, milan...@gmail.com wrote:
> 
> Hello,
> 
> Does VPP (19.04/19.08). presently support anything similar to "ip tcp 
> adjust-mss" seen in Cisco routers for example..   As in, modifying the MSS 
> for transiting TCP syn packets, to account for any overlay encapsulations 
> like vxlan.
> 
> Is it planned for any future release?
> 
> Thanks,
> Milan -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#14160): https://lists.fd.io/g/vpp-dev/message/14160
> Mute This Topic: https://lists.fd.io/mt/34484784/675193
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [otr...@employees.org]
> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14163): https://lists.fd.io/g/vpp-dev/message/14163
Mute This Topic: https://lists.fd.io/mt/34484784/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Issue with cpu jitters

2019-10-11 Thread jerryian

Hi all，when running multiple VPP instances on one node，results in linux cpu 
jitters。
# turbostat -i 1
turbostat：cpu5 jitter 5084 22080
turbostat：cpu29 jitter 5020 21292

Has anyone ever encountered this problem? How to solve it ？
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14162): https://lists.fd.io/g/vpp-dev/message/14162
Mute This Topic: https://lists.fd.io/mt/34485203/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] OpenStack Open Source Cloud Computing Software » Message: Networking-vpp 19.08.1 for VPP 19.08.1 is now available

2019-10-11 Thread Jerome Tollet via Lists.Fd.Io

Hello,
This message may be or interest to you: 
http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010073.html
Jerome
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14161): https://lists.fd.io/g/vpp-dev/message/14161
Mute This Topic: https://lists.fd.io/mt/34485126/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Any equivalent of "ip tcp adjust-mss" command in VPP

2019-10-11 Thread milanvpp

Hello,

Does VPP (19.04/19.08). presently support anything similar to "ip tcp 
adjust-mss" seen in Cisco routers for example..   As in, modifying the MSS for 
transiting TCP syn packets, to account for any overlay encapsulations like 
vxlan.

Is it planned for any future release?

Thanks,
Milan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14160): https://lists.fd.io/g/vpp-dev/message/14160
Mute This Topic: https://lists.fd.io/mt/34484784/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

Re: [vpp-dev] tls close from cli lead to assert error

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation

[vpp-dev] tls close from cli lead to assert error

Re: [vpp-dev] Any equivalent of "ip tcp adjust-mss" command in VPP

[vpp-dev] Issue with cpu jitters

[vpp-dev] OpenStack Open Source Cloud Computing Software » Message: Networking-vpp 19.08.1 for VPP 19.08.1 is now available

[vpp-dev] Any equivalent of "ip tcp adjust-mss" command in VPP

11 matches

Site Navigation

Mail list logo

Footer information