Date: Wed, 15 Apr 2026 22:37:08 +0200 From: Michael Tuexen <tuexen@FreeBSD.org> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: freebsd-current@freebsd.org Subject: Re: LRO Kernel Panic on Hyper-V VM Message-ID: <F187DF29-735F-4299-B118-F2D50A78911E@FreeBSD.org> In-Reply-To: <58C7670B-6D2A-402B-BBB8-865D652B9B08@FreeBSD.org> References: <xyi67cvnu3hpk5imd4n4e4j2jjtk2xgvbtuwaa76wrs4h4p5am@dnjvime5rjmx> <58C7670B-6D2A-402B-BBB8-865D652B9B08@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
> On 15. Apr 2026, at 22:12, Michael Tuexen <tuexen@freebsd.org> wrote: > >> On 15. Apr 2026, at 21:32, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: >> >> Hey all, >> >> I've updated one of my Hyper-V VMs earlier today against an up-to-date >> source tree. I've noticed quite a few networking-related changes in >> FreeBSD on 16-CURRENT and I suspect (at least) one of those changes is >> problematic. >> >> I'm not at all well-versed in the networking code, so I'm unsure >> what's going on. >> >> I've uploaded a core.txt dump: >> https://hardenedbsd.org/~shawn/2026-04-15_lro-panic-r01.txt > Thanks. The problem is that the vnet is not set correctly. > > This should fix it: > https://reviews.freebsd.org/D56420 The fix has been committed: https://cgit.FreeBSD.org/src/commit/?id=2d13620c6e1be7f8136095f648a6b824158d0941 <https://cgit.freebsd.org/src/commit/?id=2d13620c6e1be7f8136095f648a6b824158d0941>; Thanks for reporting the issue! Best regards Michael > > Best regards > Michael >> >> Thanks, >> >> -- >> Shawn Webb >> Cofounder / Security Engineer >> HardenedBSD >> >> Signal Username: shawn_webb.74 >> Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50 >> https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc > >home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F187DF29-735F-4299-B118-F2D50A78911E>