Date: Wed, 21 Jun 2023 18:22:52 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 272089] FreeBSD -CURRENT panic: panic invalid slot (wg(4) related) Message-ID: <bug-272089-7501-B6OO7tVUZ9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272089-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-272089-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=3D272089 Kyle Evans <kevans@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emaste@freebsd.org, | |jhb@FreeBSD.org, | |kevans@freebsd.org, | |net@FreeBSD.org Assignee|net@FreeBSD.org |kevans@freebsd.org --- Comment #1 from Kyle Evans <kevans@freebsd.org> --- >From the backtrace, it looks like MOD_LOAD is failing and so we MOD_UNLOAD = it, but it's only partially initialized and we aren't expecting that. I suspect= we should just drop all of the free stuff in wg_module_init() and let MOD_UNLO= AD deal with it, though in wg_module_deinit() we also need to avoid calling osd_jail_deregister() if wg_osd_jail_slot =3D=3D 0 (i.e. we didn't reach th= at far in initialization). --=20 You are receiving this mail because: You are on the CC list for the bug. 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-272089-7501-B6OO7tVUZ9>