Date: Thu, 10 Jun 2021 09:36:47 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 241954] netgraph: Fails on concurrent node rename Message-ID: <bug-241954-7501-RXmWNVIv8d@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241954-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-241954-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=3D241954 --- Comment #8 from commit-hook@FreeBSD.org --- A commit in branch stable/11 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3Db57a593cb2d69a684e4be04e8cea7fe7a= 7f43b24 commit b57a593cb2d69a684e4be04e8cea7fe7a7f43b24 Author: Lutz Donnerhacke <donner@FreeBSD.org> AuthorDate: 2021-05-04 19:20:39 +0000 Commit: Lutz Donnerhacke <donner@FreeBSD.org> CommitDate: 2021-06-10 09:35:21 +0000 netgraph/ng_base: Renaming a node to the same name is a noop Detailed analysis in https://github.com/genneko/freebsd-vimage-jails/issues/2 brought the problem down to a double call of ng_node_name() before and after a vnet move. Because the name of the node is already known (occupied by itself), the second call fails. PR: 241954 Reported by: Paul Armstrong Differential Revision: https://reviews.freebsd.org/D30110 (cherry picked from commit 0345fd891fe13a191fc0fae9463ea9458bfaff5a) sys/netgraph/ng_base.c | 4 ++++ 1 file changed, 4 insertions(+) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241954-7501-RXmWNVIv8d>