From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: Mlx4: BUG: unable to handle kernel at ffffffffa02be210 Date: Thu, 9 Jul 2015 16:57:31 +0300 Message-ID: <559E7DCB.5040000@mellanox.com> References: <559D1562.2070309@mellanox.com> <559D2A80.4040909@mellanox.com> <559E592D.5000201@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jack Wang Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Jack Morgenstein , Moni Shoua List-Id: linux-rdma@vger.kernel.org On 7/9/2015 4:35 PM, Jack Wang wrote: > We have other kernel modules together also the autotest > infrastructure. It's not that easy to install a 3.18.14 kernel. you said you are running on 3.18.14 and just replaced their stock RDMA stack with MLNX OFED > > I look into the code a little bit. I think the bug may relate > radix_tree usage in mlx4_cq_free , OFED code in radix_tree_delete > before synchronize_irq, but mainline code call radix_tree_delete after > synchronize_irq, does this matter? possibly yes, as in life location && timings matter > I'm building a new kernel with > this small change: -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html