From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 358] KNI packets dropped on ARM
Date: Mon, 28 Oct 2019 14:53:49 +0000 [thread overview]
Message-ID: <bug-358-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=358
Bug ID: 358
Summary: KNI packets dropped on ARM
Product: DPDK
Version: 19.08
Hardware: ARM
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: michael.pfeiffer@tu-ilmenau.de
Target Milestone: ---
Our DPDK application sends some management packets to a KNI device to be
processed by another applicton. This works fine on x86, but on an ARM Box
(Mellanox Bluefield, Kernel 4.20.17), all frames to the KNI are dropped,
including Pings, ARP, NDP, and so on.
The frames are still visible for tcpdump (and seem ok there), but are not
processed any further. A perf on del_skb gives the following backtrace:
> kni_single 9643 [015] 699.450949: skb:kfree_skb:
> skbaddr=0xffff8003fc406100 > protocol=0 location=0xffff000008c9f4bc
> ffff000008c846b8 kfree_skb+0xc8 ([kernel.kallsyms])
> ffff000008c846b8 kfree_skb+0xc8 ([kernel.kallsyms])
> ffff000008c9f4bc __netif_receive_skb_core+0x674 ([kernel.kallsyms])
> ffff000008c9fa04 __netif_receive_skb_one_core+0x4c
> ([kernel.kallsyms])
> ffff000008c9fab0 __netif_receive_skb+0x28 ([kernel.kallsyms])
> ffff000008c9fbac process_backlog+0xa4 ([kernel.kallsyms])
> ffff000008ca026c net_rx_action+0x10c ([kernel.kallsyms])
> ffff000008081ce8 __softirqentry_text_start+0x118 ([kernel.kallsyms])
> ffff0000080f0b7c do_softirq.part.3+0x54 ([kernel.kallsyms])
> ffff0000080f0c74 do_softirq+0x24 ([kernel.kallsyms])
> ffff000008c9e94c netif_rx_ni+0x124 ([kernel.kallsyms])
> ffff000000e6b570 kni_net_rx_normal+0x1f8 ([rte_kni])
> ffff000000e6c428 kni_net_rx+0x28 ([rte_kni])
> ffff000000e6ab70 kni_thread_single+0x68 ([rte_kni])
> ffff0000081109d4 kthread+0x134 ([kernel.kallsyms])
> ffff000008085f54 ret_from_fork+0x10 ([kernel.kallsyms])
Please let me know if there is any further information I could provide.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-10-28 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-358-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).