[Bug 241954] netgraph: Fails on concurrent node rename
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 10 Jun 2021 09:31:42 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241954
--- Comment #6 from commit-hook@FreeBSD.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=37370a6773cde7fcae063aed0a4cc024f95534bd
commit 37370a6773cde7fcae063aed0a4cc024f95534bd
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:29:34 +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(+)
--
You are receiving this mail because:
You are on the CC list for the bug.