[Bug 241954] netgraph: Fails on concurrent node rename

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 10 Jun 2021 09:34:46 UTC

--- Comment #7 from commit-hook@FreeBSD.org ---
A commit in branch stable/12 references this bug:


commit a0694da5d035ea0e686ad1bae95709e52df0913a
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:33:19 +0000

    netgraph/ng_base: Renaming a node to the same name is a noop

    Detailed analysis in
    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.