Re: [tipc-discussion] TIPC compatibility with different kernels

Hi Amar, The claim that TIPC is compatible between different kernel versions is true, and we always test for backwards compatibility when we introduce changes that may cause compatibility problems. However, you kernel 3.2.0 i on node 1.1.6 is *very* old, and I don't think anybody of us is

Re: [tipc-discussion] v4.7: soft lockup when releasing a socket

Hi John, Regarding the stack trace you provided below, I get the two potential call chains: tipc_nametbl_withdraw spin_lock_bh(>nametbl_lock); tipc_nametbl_remove_publ spin_lock_bh(>lock); tipc_nameseq_remove_publ tipc_subscrp_report_overlap tipc_subscrp_send_event

Re: [tipc-discussion] v4.7: soft lockup when releasing a socket

Hi John, The nametbl_lock deadlock is caused at the module/namespace exit, when tipc_net_stop() and tipc_topsrv_stop() are running in parallel. #CPU 0 tipc_net_stop() calls tipc_nametbl_withdraw() grabs the spinlock and further down the callchain calls tipc_conn_sendmsg(). #CPU 1

[tipc-discussion] TIPC compatibility with different kernels

Hello, I am trying to bring up a cluster of 2 nodes hosted on different environments. *NODE1 TIPC Node-addr (6)*root@host1:/lib/modules/3.2.0-29-generic/kernel/net/tipc# modinfo tipc.ko filename: tipc.ko version:2.0.0 license:Dual BSD/GPL description:TIPC: Transparent