Zoltan Kiss e3377f36ca xen-netback: Handle guests with too many frags ... Xen network protocol had implicit dependency on MAX_SKB_FRAGS. Netback has to handle guests sending up to XEN_NETBK_LEGACY_SLOTS_MAX slots. To achieve that: - create a new skb - map the leftover slots to its frags (no linear buffer here!) - chain it to the previous through skb_shinfo(skb)->frag_list - map them - copy and coalesce the frags into a brand new one and send it to the stack - unmap the 2 old skb's pages It's also introduces new stat counters, which help determine how often the guest sends a packet with more than MAX_SKB_FRAGS frags. NOTE: if bisect brought you here, you should apply the series up until "xen-netback: Timeout packets in RX path", otherwise malicious guests can block other guests by not releasing their sent packets. Signed-off-by: Zoltan Kiss <zoltan.kiss@citrix.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2014-03-07 15:56:35 -05:00
..
common.h	xen-netback: Handle guests with too many frags	2014-03-07 15:56:35 -05:00
interface.c	xen-netback: Handle guests with too many frags	2014-03-07 15:56:35 -05:00
Makefile
netback.c	xen-netback: Handle guests with too many frags	2014-03-07 15:56:35 -05:00
xenbus.c	drivers/net/*: Fix FSF address in file headers	2013-12-06 12:37:55 -05:00