[Bug 216304] Adding xn0 to bridge0 causes kernel panic
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Feb 1 20:27:45 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216304
--- Comment #8 from commit-hook at freebsd.org ---
A commit references this bug:
Author: kp
Date: Wed Feb 1 20:27:38 UTC 2017
New revision: 313050
URL: https://svnweb.freebsd.org/changeset/base/313050
Log:
MFC 312782
bridge: Release the bridge lock when calling bridge_set_ifcap()
This calls ioctl() handlers for the different interfaces in the bridge.
These handlers expect to get called in an ioctl context where it's safe
for them to sleep. We may not sleep with the bridge lock held.
However, we still need to protect the interface list, to ensure it
doesn't get changed while we iterate over it.
Use BRIDGE_XLOCK(), which prevents bridge members from being removed.
Adding bridge members is safe, because it uses LIST_INSERT_HEAD().
This caused panics when adding xen interfaces to a bridge.
PR: 216304
Reviewed by: ae
Sponsored by: RootBSD
Differential Revision: https://reviews.freebsd.org/D9290
Changes:
_U stable/11/
stable/11/sys/net/if_bridge.c
stable/11/sys/net/if_bridgevar.h
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-net
mailing list