Hi Rune, The recent tipc changes related to topology server are not applied to Ubuntu mainline kernel, as this is based on 4.4 kernel. I think we have a new issue here, as the recent fixes were related to subscription handling and your issue seems to be a race between publication and withdrawal of nametable entries.
How do you trigger this fault? Does your application do repeated publish and withdraw? regards Partha On 05/20/2016 06:10 PM, Rune Torgersen wrote: > Was all the tipc changes ported to the Ubuntu mainline kernel (16.04LTS, > 4.4.0-22-generic)? > > I got this particular crash today: > > [682190.533680] BUG: unable to handle kernel NULL pointer dereference at > (null) > [682190.534571] IP: [<ffffffffc053e2d3>] tipc_nameseq_remove_publ+0x1b3/0x220 > [tipc] > [682190.535461] PGD 0 > [682190.536313] Oops: 0000 [#1] SMP > [682190.537176] Modules linked in: btrfs ufs qnx4 hfsplus hfs minix ntfs > msdos jfs xfs tipc cls_fw sch_sfq sch_htb xt_CLASSIFY xt_multiport > iptable_mangle ip_tables x_tables nls_iso8859_1 quota_v2 mvsas quota_tree > ixgbe libsas mei_me igb vxlan mei scsi_transport_sas ip6_udp_tunnel > udp_tunnel intel_rapl ptp lpc_ich pps_core mdio acpi_pad acpi_power_meter > fjes x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass > crct10dif_pclmul crc32_pclmul input_leds ipmi_ssif cryptd joydev hid_generic > sb_edac 8250_fintek shpchp edac_core usbhid hid ioatdma dca mac_hid ib_iser > rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp > libiscsi scsi_transport_iscsi ipmi_si ipmi_devintf ipmi_msghandler autofs4 > raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor xor > [682190.543356] async_tx raid6_pq raid1 raid0 multipath linear ast > i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops > drm ahci libahci wmi > [682190.545761] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W > 4.4.0-22-generic #39-Ubuntu > [682190.547006] Hardware name: Supermicro Super Server/X10SRL-F, BIOS 1.0b > 04/17/2015 > [682190.548264] task: ffffffff81e11500 ti: ffffffff81e00000 task.ti: > ffffffff81e00000 > [682190.549582] RIP: 0010:[<ffffffffc053e2d3>] [<ffffffffc053e2d3>] > tipc_nameseq_remove_publ+0x1b3/0x220 [tipc] > [682190.550939] RSP: 0018:ffff88103cc03a40 EFLAGS: 00010213 > [682190.552251] RAX: 0000000000000000 RBX: ffff88010e40de00 RCX: > 0000000000000002 > [682190.553649] RDX: 0000000000000009 RSI: 0000000000000009 RDI: > ffff8809a0a6f200 > [682190.555051] RBP: ffff88103cc03a80 R08: 00000000e7f01c05 R09: > 0000000001001001 > [682190.556456] R10: 0000000000000000 R11: 0000000000000005 R12: > ffffffffffffff80 > [682190.557918] R13: ffff881031000520 R14: ffff881031aa9ce8 R15: > 0000000000000000 > [682190.559393] FS: 0000000000000000(0000) GS:ffff88103cc00000(0000) > knlGS:0000000000000000 > [682190.560866] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [682190.562404] CR2: 0000000000000000 CR3: 000000107ee0a000 CR4: > 00000000001406f0 > [682190.563936] Stack: > [682190.565450] ffffffff00000000 0000000101001001 ffff881031aa9cc0 > ffffffff81ef3ec0 > [682190.567070] ffff881031aa9cf8 ffff881031aa9cc0 00000000e7f01c05 > 00000000e7f01c06 > [682190.568683] ffff88103cc03ac0 ffffffffc053e929 0000000901001001 > 0000000001001001 > [682190.570325] Call Trace: > [682190.571972] <IRQ> > [682190.571996] [<ffffffffc053e929>] tipc_nametbl_remove_publ+0x59/0xe0 > [tipc] > [682190.575307] [<ffffffffc053ce2e>] tipc_update_nametbl+0xfe/0x170 [tipc] > [682190.577017] [<ffffffffc053d63a>] tipc_named_rcv+0xea/0x1e0 [tipc] > [682190.578761] [<ffffffffc0542fce>] ? tipc_node_unlock+0x2e/0xe0 [tipc] > [682190.580479] [<ffffffffc0543f95>] tipc_rcv+0x3b5/0xcb0 [tipc] > [682190.582179] [<ffffffff81759620>] ? ip_rcv_finish+0x320/0x320 > [682190.583890] [<ffffffffc053554d>] tipc_l2_rcv_msg+0x3d/0x50 [tipc] > [682190.585551] [<ffffffff8171b314>] __netif_receive_skb_core+0x704/0xa60 > [682190.587242] [<ffffffff8178c327>] ? udp4_gro_receive+0x1c7/0x2e0 > [682190.588899] [<ffffffff8171b688>] __netif_receive_skb+0x18/0x60 > [682190.590520] [<ffffffff8171b702>] netif_receive_skb_internal+0x32/0xa0 > [682190.592166] [<ffffffff8171c383>] napi_gro_receive+0xc3/0x120 > [682190.593774] [<ffffffffc04c4cc7>] igb_clean_rx_irq+0x6f7/0x790 [igb] > [682190.595408] [<ffffffffc04c50ba>] igb_poll+0x35a/0x710 [igb] > [682190.596983] [<ffffffff810aae74>] ? check_preempt_curr+0x54/0x90 > [682190.598550] [<ffffffff810ab02d>] ? > ttwu_do_activate.constprop.90+0x5d/0x70 > [682190.600135] [<ffffffff8171bbce>] net_rx_action+0x21e/0x360 > [682190.601679] [<ffffffff810859f1>] __do_softirq+0x101/0x290 > [682190.603191] [<ffffffff81085cf3>] irq_exit+0xa3/0xb0 > [682190.604716] [<ffffffff81827ce4>] do_IRQ+0x54/0xd0 > [682190.606215] [<ffffffff81825dc2>] common_interrupt+0x82/0x82 > [682190.607695] <EOI> > [682190.607715] [<ffffffff816bc411>] ? cpuidle_enter_state+0x111/0x2b0 > [682190.610558] [<ffffffff816bc3ff>] ? cpuidle_enter_state+0xff/0x2b0 > [682190.611924] [<ffffffff816bc5e7>] cpuidle_enter+0x17/0x20 > [682190.613251] [<ffffffff810c3db2>] call_cpuidle+0x32/0x60 > [682190.614543] [<ffffffff816bc5c3>] ? cpuidle_select+0x13/0x20 > [682190.615789] [<ffffffff810c4070>] cpu_startup_entry+0x290/0x350 > [682190.617016] [<ffffffff81818d2c>] rest_init+0x7c/0x80 > [682190.618199] [<ffffffff81f5a011>] start_kernel+0x481/0x4a2 > [682190.619353] [<ffffffff81f59120>] ? early_idt_handler_array+0x120/0x120 > [682190.620519] [<ffffffff81f59339>] x86_64_start_reservations+0x2a/0x2c > [682190.621653] [<ffffffff81f59485>] x86_64_start_kernel+0x14a/0x16d > [682190.622756] Code: 80 4c 8d 66 80 74 38 8b 53 08 44 8b 4b 10 b9 02 00 00 > 00 44 8b 43 14 8b 73 04 44 89 3c 24 e8 f5 fb ff ff 49 8d 84 24 80 00 00 00 > <49> 8b 94 24 80 00 00 00 4c 89 e7 4c 39 f0 4c 8d 62 80 75 c8 48 > [682190.625212] RIP [<ffffffffc053e2d3>] > tipc_nameseq_remove_publ+0x1b3/0x220 [tipc] > [682190.626399] RSP <ffff88103cc03a40> > [682190.627538] CR2: 0000000000000000 > > ------------------------------------------------------------------------------ > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j > _______________________________________________ > tipc-discussion mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/tipc-discussion ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
