John Fastabend 2df4a0fa15 net: fix conflict between null_or_orig and null_or_bond ... If a skb is received on an inactive bond that does not meet the special cases checked for by skb_bond_should_drop it should only be delivered to exact matches as the comment in netif_receive_skb() says. However because null_or_bond could also be null this is not always true. This patch renames null_or_bond to orig_or_bond and initializes it to orig_dev. This keeps the intent of null_or_bond to pass frames received on VLAN interfaces stacked on bonding interfaces without invalidating the statement for null_or_orig. Signed-off-by: John Fastabend <john.r.fastabend@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2010-06-02 03:35:18 -07:00
..
datagram.c
dev_addr_lists.c
dev.c	net: fix conflict between null_or_orig and null_or_bond	2010-06-02 03:35:18 -07:00
drop_monitor.c
dst.c
ethtool.c
fib_rules.c
filter.c
flow.c
gen_estimator.c
gen_stats.c
iovec.c
kmap_skb.h
link_watch.c
Makefile
neighbour.c
net_namespace.c
net-sysfs.c
net-sysfs.h
net-traces.c
netevent.c
netpoll.c
pktgen.c
request_sock.c
rtnetlink.c
scm.c
skbuff.c	net: sock_queue_err_skb() dont mess with sk_forward_alloc	2010-05-31 23:44:05 -07:00
sock.c
stream.c
sysctl_net_core.c
user_dma.c
utils.c