Date: Fri, 26 Aug 2022 21:46:31 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 266054] panic: page fault in sys/ofed/drivers/infiniband/core/ib_cma.c:1060 Message-ID: <bug-266054-7501-OtWBeduOOE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266054-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-266054-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266054 Eric Joyner <erj@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erj@freebsd.org --- Comment #3 from Eric Joyner <erj@freebsd.org> --- I think I can help; I discovered this already: (we had a little Twitter thr= ead) https://twitter.com/kaevans91/status/1557167097813278722 The tl;dr is that the V_in_loopback_mask variable (that gets accessed from within cma_loopback_addr via the ipv4 loopback check) got added in a previo= us commit but that RDMA code doesn't have the currvnet set, so the vnet that g= ets checked in V_in_loopback_mask is NULL and the kernel panics. IPv6 code in RDMA doesn't seem to use anything VIMAGE-related so that isn't affected by this issue; you can IPv6 ping as a workaround for now. But krpi= ng is IPv4 only, so that's currently unusable. I think there are other IPv4 places in OFED that also need fixing, like validate_ipv4_net_dev(). I tried looking around, but never got around to properly finishing a patch that I was working on. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266054-7501-OtWBeduOOE>