netdev - xdp_router_ipv4 mellanox problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <e14d6471-ece3-202d-9af0-fbac0f7edcab@itcare.pl>
Date:   Mon, 29 Jan 2018 17:15:17 +0100
From:   Paweł Staszewski <pstaszewski@...are.pl>
To:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: xdp_router_ipv4 mellanox problem

Hi

Want to do some tests with xdp_router on two 100G physical interfaces but:

Jan 29 17:00:40 HOST kernel: mlx5_core 0000:af:00.0: MLX5E: StrdRq(0) 
RqSz(1024) StrdSz(1) RxCqeCmprss(0)
Jan 29 17:00:40 HOST kernel: mlx5_core 0000:af:00.0 enp175s0f0: Link up
Jan 29 17:00:41 HOST kernel: mlx5_core 0000:af:00.1: MLX5E: StrdRq(0) 
RqSz(1024) StrdSz(1) RxCqeCmprss(0)
Jan 29 17:00:41 HOST kernel: mlx5_core 0000:af:00.1 enp175s0f1: Link up
Jan 29 17:00:41 HOST kernel: ------------[ cut here ]------------
Jan 29 17:00:41 HOST kernel: Driver unsupported XDP return value 4, 
expect packet loss!
Jan 29 17:00:41 HOST kernel: WARNING: CPU: 43 PID: 0 at 
net/core/filter.c:3901 bpf_warn_invalid_xdp_action+0x34/0x40
Jan 29 17:00:41 HOST kernel: Modules linked in: x86_pkg_temp_thermal ipmi_si
Jan 29 17:00:41 HOST kernel: CPU: 43 PID: 0 Comm: swapper/43 Not tainted 
4.15.0-rc9+ #1
Jan 29 17:00:41 HOST kernel: RIP: 0010:bpf_warn_invalid_xdp_action+0x34/0x40
Jan 29 17:00:41 HOST kernel: RSP: 0018:ffff88087f9c3dc8 EFLAGS: 00010296
Jan 29 17:00:41 HOST kernel: RAX: 000000000000003a RBX: ffff88081ea38000 
RCX: 0000000000000006
Jan 29 17:00:41 HOST kernel: RDX: 0000000000000007 RSI: 0000000000000092 
RDI: ffff88087f9d53d0
Jan 29 17:00:41 HOST kernel: RBP: ffff88087f9c3e58 R08: 0000000000000001 
R09: 0000000000000536
Jan 29 17:00:41 HOST kernel: R10: 0000000000000004 R11: 0000000000000536 
R12: ffff8808304d3000
Jan 29 17:00:41 HOST kernel: R13: 00000000000002c0 R14: ffff88081e53c000 
R15: ffffc9000007d000
Jan 29 17:00:41 HOST kernel: FS:  0000000000000000(0000) 
GS:ffff88087f9c0000(0000) knlGS:0000000000000000
Jan 29 17:00:41 HOST kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 
0000000080050033
Jan 29 17:00:41 HOST kernel: CR2: 0000000002038648 CR3: 000000000220a002 
CR4: 00000000007606e0
Jan 29 17:00:41 HOST kernel: DR0: 0000000000000000 DR1: 0000000000000000 
DR2: 0000000000000000
Jan 29 17:00:41 HOST kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 
DR7: 0000000000000400
Jan 29 17:00:41 HOST kernel: PKRU: 55555554
Jan 29 17:00:41 HOST kernel: Call Trace:
Jan 29 17:00:41 HOST kernel:  <IRQ>
Jan 29 17:00:41 HOST kernel:  mlx5e_handle_rx_cqe+0x279/0x900
Jan 29 17:00:41 HOST kernel:  mlx5e_poll_rx_cq+0xb3/0x860
Jan 29 17:00:41 HOST kernel:  mlx5e_napi_poll+0x81/0x6f0
Jan 29 17:00:41 HOST kernel:  ? mlx5_cq_completion+0x4d/0xb0
Jan 29 17:00:41 HOST kernel:  net_rx_action+0x1cd/0x2f0
Jan 29 17:00:41 HOST kernel:  __do_softirq+0xe4/0x275
Jan 29 17:00:41 HOST kernel:  irq_exit+0x6b/0x70
Jan 29 17:00:41 HOST kernel:  do_IRQ+0x45/0xc0
Jan 29 17:00:41 HOST kernel:  common_interrupt+0x95/0x95
Jan 29 17:00:41 HOST kernel:  </IRQ>
Jan 29 17:00:41 HOST kernel: RIP: 0010:mwait_idle+0x59/0x160
Jan 29 17:00:41 HOST kernel: RSP: 0018:ffffc90003497ef8 EFLAGS: 00000246 
ORIG_RAX: ffffffffffffffdd
Jan 29 17:00:41 HOST kernel: RAX: 0000000000000000 RBX: 000000000000002b 
RCX: 0000000000000000
Jan 29 17:00:41 HOST kernel: RDX: 0000000000000000 RSI: 0000000000000000 
RDI: 0000000000000000
Jan 29 17:00:41 HOST kernel: RBP: 000000000000002b R08: 0000000000001000 
R09: 0000000000000000
Jan 29 17:00:41 HOST kernel: R10: 0000000000000000 R11: 0000000100130e40 
R12: ffff88086d165000
Jan 29 17:00:41 HOST kernel: R13: ffff88086d165000 R14: 0000000000000000 
R15: 0000000000000000
Jan 29 17:00:41 HOST kernel:  do_idle+0x14e/0x160
Jan 29 17:00:41 HOST kernel:  cpu_startup_entry+0x14/0x20
Jan 29 17:00:41 HOST kernel:  secondary_startup_64+0xa5/0xb0
Jan 29 17:00:41 HOST kernel: Code: c3 83 ff 04 48 c7 c0 1a cf 10 82 89 
fa c6 05 9a df b4 00 01 48 c7 c6 22 cf 10 82 48 c7 c7 38 cf 10 82 48 0f 
47 f0 e8 ec 19 8b ff <0f> ff c3 66 0f 1f 84 00 00 00 00 00 81 fe ff ff 
00 00 55 48 89
Jan 29 17:00:41 HOST kernel: ---[ end trace 2b255fac8d0824de ]---


I can attach xdp_router_ipv4 to any vlan interface without crash

./xdp_router_ipv4 vlan4032

**************loading bpf file*********************


Attached to 8
*******************ROUTE TABLE*************************


NEW Route entry
Destination             Gateway         Genmask Metric          Iface
192.168.32.0              0             24 0               vlan4032
*******************ARP TABLE***************************


Address HwAddress
7920a8c0                8da6fb902500
120a8c0         44fc9e0c5e4c



But after attaching to physical interface there is "above trace".



Thanks

Paweł