DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] KNI crashes when invalid lldp frames are received
@ 2016-01-04  6:18 laxmi.priya
  0 siblings, 0 replies; only message in thread
From: laxmi.priya @ 2016-01-04  6:18 UTC (permalink / raw)
  To: dev

Hi,


We are using OVS 2.4 with DPDK 2.0 with  kernel 3.18.22. Default flow rules i.e NORMAL rules are there.KNI port is a member port of the ovs bridge

We are using Openmul controller and when invoke the set-controller command i.e ovs-vsctl --no-wait set-controller br0  tcp:127.0.0.1:6653, kni crashes with the below stack


<4>Stack:
<4> ffff880153937d48 ffff880153937d50 ffff880150814000 0000000000000001
<4> 000000002138f240 ffffffff810cf36b ffff880153937df8 ffffffff82055980
<4> 0000000100250151 0000000000000282 ffff880153937da8 ffffffff810d042f
<4>Call Trace:
<4> [<ffffffff810cf36b>] ? lock_timer_base.isra.35+0x2b/0x50
<4> [<ffffffff810d042f>] ? try_to_del_timer_sync+0x4f/0x70
<4> [<ffffffff810d04a2>] ? del_timer_sync+0x52/0x60
<4> [<ffffffff81653bb6>] ? schedule_timeout+0x166/0x290
<4> [<ffffffff810cf240>] ? internal_add_timer+0x80/0x80
<4> [<ffffffffa041743f>] kni_net_rx+0xf/0x20 [rte_kni]
<4> [<ffffffffa041577e>] kni_thread_single+0x5e/0xb0 [rte_kni]
<4> [<ffffffffa0415720>] ? kni_release+0x100/0x100 [rte_kni]
<4> [<ffffffff81089bc9>] kthread+0xc9/0xe0
<4> [<ffffffff81089b00>] ? kthread_create_on_node+0x180/0x180
<4> [<ffffffff81654f18>] ret_from_fork+0x58/0x90
<4> [<ffffffff81089b00>] ? k:q+0x180/0x180
<4>Code: 48 89 85 b8 fe ff ff eb 0c 0f 1f 44 00 00 48 8b 13 48 83 c3 08 49 8b 8d a8 01 00 00 4d

8b b5 a0 01 00 00 31 ff 48 29 ca 4c 01 f2 <44> 0f b7 62 22 0f b7 42 12 48 03 02 ba 20 00 00 00

45 0f b7 cc
<1>RIP  [<ffffffffa0416905>] kni_net_rx_normal+0x145/0x2c0 [rte_kni]
<4> RSP <ffff880153937d28>
<4>---[ end trace 8a2acec3270c7c4b ]---



During debugging we could see that the lldp frames are transmitted on the bridge ports whenever the controller is attached .

But those lldp frames were invalid and had the data_offset of the struct rte_mbuf packets set to 2.

Normal packets if we check could see that the data offset is equal to RTE_PKTMBUF_HEADROOM ( i.e 128. )

Is there any limitation in KNI that the packet data offset should be equal to or greater than RTE_PKTMBUF_HEADROOM



Regards

Laxmi

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-01-04  6:19 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-04  6:18 [dpdk-dev] KNI crashes when invalid lldp frames are received laxmi.priya

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).