Date: Thu, 07 Sep 2023 15:50:20 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 273557] Regression preventing bhyve from running inside a jail without IP after f74147e26999838e03a522bf59ea33bef470d356) breaks support for jailing bhyve with IPv4 and IPv6 disabled. Patch included. Message-ID: <bug-273557-27103-Uqe6p8L1KE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273557-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-273557-27103@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=3D273557 --- Comment #5 from crest@rlwinm.de --- (In reply to Bjoern A. Zeeb from comment #3) I've seen that the ioctl() does implicitly bitwise-or in the IFF_UP flag, b= ut it felt cleaner to explicitly request this instead of relying on this undocumented implementation detail. I confirmed it even brings the interfac= e up if a NULL pointer is passed as argument to the ioctl(), but again that woul= d be an ugly workaround. I agree that it would've been better to make this optio= nal or even check the interface link state before overwriting it and only refus= ing to start the guest if the link can't be brought up, but I don't see any situation where the current implementation of the VMIO_SIOCSIFFLAGS ioctl() would fail on an opened tap device so the error handling code is unreachabl= e on FreeBSD releng/13.2 and stable/14. --=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-273557-27103-Uqe6p8L1KE>