Date: Wed, 21 Feb 2024 22:08:51 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 185619] [VNET] Name conflict not checked when a child vnet goes away and returns its interface(s) back to the parent Message-ID: <bug-185619-227-6bmb7j9ghh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-185619-227@https.bugs.freebsd.org/bugzilla/> References: <bug-185619-227@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=3D185619 c433li@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |c433li@gmail.com --- Comment #6 from c433li@gmail.com --- Just encountered this issue on 14.0-RELEASE. > Option 1: Give the returned interface a random, unique name. Since jids are never recycled, does this approach really have to be non-deterministic? I mean, it seems to me that we could make up some sort of convention that interfaces recycled from a destroyed vnet be given a special name such as `<if_type>_recycle_<jid>`, and for hierarchical jails we can append the nested jids to it, such as `<if_type>_recycle_<jid>_<nested_jid>= `. It is still possible to have naming conflict if the user insist on renaming their interface to one of these "special" names, but this approach can eliminate the majority of these conflicts without architectural changes. --=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-185619-227-6bmb7j9ghh>