[Bug 241954] netgraph fails on concurrent node rename
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 04 Jun 2021 09:22:36 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241954
--- Comment #4 from commit-hook@FreeBSD.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=0345fd891fe13a191fc0fae9463ea9458bfaff5a
commit 0345fd891fe13a191fc0fae9463ea9458bfaff5a
Author: Lutz Donnerhacke <donner@FreeBSD.org>
AuthorDate: 2021-05-04 19:20:39 +0000
Commit: Lutz Donnerhacke <donner@FreeBSD.org>
CommitDate: 2021-06-04 09:20:19 +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
MFC: 1 week
Differential Revision: https://reviews.freebsd.org/D30110
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.