Allow vlan interfaces to rx through netmap(4).
Normally after receiving a packet, a vlan(4) interface sends the packet back through its parent interface's rx routine so that it can be processed as an untagged frame. It does this by using the parent's ifp->if_input. This is incompatible with netmap(4), which replaces the vlan(4) interface's if_input with a netmap(4) hook. Fix this by using the vlan(4) interface's ifp instead of the parent's directly. Reported by: Harry Schmalzbauer <freebsd@omnilan.de> Reviewed by: rstone Approved by: rstone (mentor) MFC after: 3 days Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D12191
This commit is contained in:
parent
be17336036
commit
fdbf11746a
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=323513
@ -1384,7 +1384,7 @@ vlan_input(struct ifnet *ifp, struct mbuf *m)
|
||||
VLAN_RUNLOCK();
|
||||
|
||||
/* Pass it back through the parent's input routine. */
|
||||
(*ifp->if_input)(ifv->ifv_ifp, m);
|
||||
(*ifv->ifv_ifp->if_input)(ifv->ifv_ifp, m);
|
||||
}
|
||||
|
||||
static void
|
||||
|
Loading…
Reference in New Issue
Block a user