We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICMP with tapv2 interfaces with jumbo frames crash in VPP master and 19.04
VPP side
DBGvpp# create tap
DBGvpp# set interface state tap0 up
DBGvpp# set interface ip address tap0 10.10.2.1/24
Linux side
jerome@jerome-virtual-machine:~/devel/vpp$ sudo ifconfig tap0 mtu 9000
jerome@jerome-virtual-machine:~/devel/vpp$ sudo ifconfig tap0 10.10.2.2/24
jerome@jerome-virtual-machine:~/devel/vpp$ ping 10.10.2.1/24 -s 30000
Here is the stack I get in in vpp:
DBGvpp#
Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault.
0x00007ffff6e0fa4f in mm256_loadu_si256 (_P=0x10027ffff4) at /usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:921
921 return *__P;
(gdb) #0 0x00007ffff6e0fa4f in mm256_loadu_si256 (_P=0x10027ffff4) at /usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:921
#1 clib_mov128blocks (dst=0x10027fffc0 "", src=0x10027fffb4 "", n=36072) at /home/jerome/devel/vpp/src/vppinfra/memcpy_avx2.h:99
#2 0x00007ffff6e0fe88 in clib_memcpy_fast (dst=0x10027f8d40, src=0x10027f8d34, n=65512)
at /home/jerome/devel/vpp/src/vppinfra/memcpy_avx2.h:218
#3 0x00007ffff6e13e2d in vlib_buffer_chain_linearize (vm=0x7ffff6cafc80 <vlib_global_main>, b=0x10027f1e80)
at /home/jerome/devel/vpp/src/vlib/buffer_funcs.h:1443
#4 0x00007ffff6e17034 in ip4_reass_finalize (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280,
rm=0x7ffff7f54160 <ip4_reass_main>, rt=0x7fffb7fa4720, reass=0x7fffb7f7b0c8, bi0=0x7fffb69fda4c, next0=0x7fffb69fda50,
error0=0x7fffb69fda54, is_feature=false) at /home/jerome/devel/vpp/src/vnet/ip/ip4_reassembly.c:581
#5 0x00007ffff6e17c62 in ip4_reass_update (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280,
error0=0x7fffb69fda54, is_feature=false) at /home/jerome/devel/vpp/src/vnet/ip/ip4_reassembly.c:936
#6 0x00007ffff6e180e5 in ip4_reassembly_inline (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280, frame=0x7fffb800afc0,
is_feature=false) at /home/jerome/devel/vpp/src/vnet/ip/ip4_reassembly.c:1038
#7 0x00007ffff6e184bf in ip4_reass_node_fn_avx2 (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280, frame=0x7fffb800afc0)
at /home/jerome/devel/vpp/src/vnet/ip/ip4_reassembly.c:1118
#8 0x00007ffff6c06381 in dispatch_node (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280, type=VLIB_NODE_TYPE_INTERNAL,
dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x7fffb800afc0, last_time_stamp=1632188766404)
at /home/jerome/devel/vpp/src/vlib/main.c:1213
#9 0x00007ffff6c06b56 in dispatch_pending_node (vm=0x7ffff6cafc80 <vlib_global_main>, pending_frame_index=4,
last_time_stamp=1632188766404) at /home/jerome/devel/vpp/src/vlib/main.c:1381
#10 0x00007ffff6c08911 in vlib_main_or_worker_loop (vm=0x7ffff6cafc80 <vlib_global_main>, is_main=1)
at /home/jerome/devel/vpp/src/vlib/main.c:1824
#11 0x00007ffff6c0918c in vlib_main_loop (vm=0x7ffff6cafc80 <vlib_global_main>) at /home/jerome/devel/vpp/src/vlib/main.c:1926
#12 0x00007ffff6c09eff in vlib_main (vm=0x7ffff6cafc80 <vlib_global_main>, input=0x7fffb69fdfb0)
at /home/jerome/devel/vpp/src/vlib/main.c:2115
#13 0x00007ffff6c76bb7 in thread0 (arg=140737333886080) at /home/jerome/devel/vpp/src/vlib/unix/main.c:640
#14 0x00007ffff6a9afb4 in clib_calljmp () from /home/jerome/devel/vpp/build-root/install-vpp_debug-native/vpp/lib/libvppinfra.so.19.08
#15 0x00007fffffffd1e0 in ?? ()
#16 0x00007ffff6c77173 in vlib_unix_main (argc=2, argv=0x7fffffffe4f8) at /home/jerome/devel/vpp/src/vlib/unix/main.c:710
#17 0x000055555555c2bc in main (argc=2, argv=0x7fffffffe4f8) at /home/jerome/devel/vpp/src/vpp/vnet/main.c:280
Ole Trøan
Jerome Tollet
Original issue: https://jira.fd.io/browse/VPP-1695
The text was updated successfully, but these errors were encountered:
Fixed by commit 7331005c16d0e1499080899b2a0676a0cd945595
Sorry, something went wrong.
No branches or pull requests
Description
ICMP with tapv2 interfaces with jumbo frames crash in VPP master and 19.04
VPP side
DBGvpp# create tap
DBGvpp# set interface state tap0 up
DBGvpp# set interface ip address tap0 10.10.2.1/24
Linux side
jerome@jerome-virtual-machine:~/devel/vpp$ sudo ifconfig tap0 mtu 9000
jerome@jerome-virtual-machine:~/devel/vpp$ sudo ifconfig tap0 10.10.2.2/24
jerome@jerome-virtual-machine:~/devel/vpp$ ping 10.10.2.1/24 -s 30000
Here is the stack I get in in vpp:
DBGvpp#
Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault.
0x00007ffff6e0fa4f in mm256_loadu_si256 (_P=0x10027ffff4) at /usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:921
921 return *__P;
(gdb) #0 0x00007ffff6e0fa4f in mm256_loadu_si256 (_P=0x10027ffff4) at /usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:921
#1 clib_mov128blocks (dst=0x10027fffc0 "", src=0x10027fffb4 "", n=36072) at /home/jerome/devel/vpp/src/vppinfra/memcpy_avx2.h:99
#2 0x00007ffff6e0fe88 in clib_memcpy_fast (dst=0x10027f8d40, src=0x10027f8d34, n=65512)
at /home/jerome/devel/vpp/src/vppinfra/memcpy_avx2.h:218
#3 0x00007ffff6e13e2d in vlib_buffer_chain_linearize (vm=0x7ffff6cafc80 <vlib_global_main>, b=0x10027f1e80)
at /home/jerome/devel/vpp/src/vlib/buffer_funcs.h:1443
#4 0x00007ffff6e17034 in ip4_reass_finalize (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280,
rm=0x7ffff7f54160 <ip4_reass_main>, rt=0x7fffb7fa4720, reass=0x7fffb7f7b0c8, bi0=0x7fffb69fda4c, next0=0x7fffb69fda50,
error0=0x7fffb69fda54, is_feature=false) at /home/jerome/devel/vpp/src/vnet/ip/ip4_reassembly.c:581
#5 0x00007ffff6e17c62 in ip4_reass_update (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280,
rm=0x7ffff7f54160 <ip4_reass_main>, rt=0x7fffb7fa4720, reass=0x7fffb7f7b0c8, bi0=0x7fffb69fda4c, next0=0x7fffb69fda50,
error0=0x7fffb69fda54, is_feature=false) at /home/jerome/devel/vpp/src/vnet/ip/ip4_reassembly.c:936
#6 0x00007ffff6e180e5 in ip4_reassembly_inline (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280, frame=0x7fffb800afc0,
is_feature=false) at /home/jerome/devel/vpp/src/vnet/ip/ip4_reassembly.c:1038
#7 0x00007ffff6e184bf in ip4_reass_node_fn_avx2 (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280, frame=0x7fffb800afc0)
at /home/jerome/devel/vpp/src/vnet/ip/ip4_reassembly.c:1118
#8 0x00007ffff6c06381 in dispatch_node (vm=0x7ffff6cafc80 <vlib_global_main>, node=0x7fffb7bf3280, type=VLIB_NODE_TYPE_INTERNAL,
dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x7fffb800afc0, last_time_stamp=1632188766404)
at /home/jerome/devel/vpp/src/vlib/main.c:1213
#9 0x00007ffff6c06b56 in dispatch_pending_node (vm=0x7ffff6cafc80 <vlib_global_main>, pending_frame_index=4,
last_time_stamp=1632188766404) at /home/jerome/devel/vpp/src/vlib/main.c:1381
#10 0x00007ffff6c08911 in vlib_main_or_worker_loop (vm=0x7ffff6cafc80 <vlib_global_main>, is_main=1)
at /home/jerome/devel/vpp/src/vlib/main.c:1824
#11 0x00007ffff6c0918c in vlib_main_loop (vm=0x7ffff6cafc80 <vlib_global_main>) at /home/jerome/devel/vpp/src/vlib/main.c:1926
#12 0x00007ffff6c09eff in vlib_main (vm=0x7ffff6cafc80 <vlib_global_main>, input=0x7fffb69fdfb0)
at /home/jerome/devel/vpp/src/vlib/main.c:2115
#13 0x00007ffff6c76bb7 in thread0 (arg=140737333886080) at /home/jerome/devel/vpp/src/vlib/unix/main.c:640
#14 0x00007ffff6a9afb4 in clib_calljmp () from /home/jerome/devel/vpp/build-root/install-vpp_debug-native/vpp/lib/libvppinfra.so.19.08
#15 0x00007fffffffd1e0 in ?? ()
#16 0x00007ffff6c77173 in vlib_unix_main (argc=2, argv=0x7fffffffe4f8) at /home/jerome/devel/vpp/src/vlib/unix/main.c:710
#17 0x000055555555c2bc in main (argc=2, argv=0x7fffffffe4f8) at /home/jerome/devel/vpp/src/vpp/vnet/main.c:280
Assignee
Ole Trøan
Reporter
Jerome Tollet
Comments
Original issue: https://jira.fd.io/browse/VPP-1695
The text was updated successfully, but these errors were encountered: