summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorSven Eckelmann <sven@narfation.org>2022-04-16 14:51:10 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-05-18 10:18:05 +0300
commit5ed837a7e05bcba72bdcd86b12547ea5b796cc01 (patch)
treea15e9c0af684006bc5e6113e4ff7a685dac858af /include/linux
parent690285a9380d183e6d286d90e458fa7c3f97eca2 (diff)
downloadlinux-5ed837a7e05bcba72bdcd86b12547ea5b796cc01.tar.xz
batman-adv: Don't skb_split skbuffs with frag_list
[ Upstream commit a063f2fba3fa633a599253b62561051ac185fa99 ] The receiving interface might have used GRO to receive more fragments than MAX_SKB_FRAGS fragments. In this case, these will not be stored in skb_shinfo(skb)->frags but merged into the frag list. batman-adv relies on the function skb_split to split packets up into multiple smaller packets which are not larger than the MTU on the outgoing interface. But this function cannot handle frag_list entries and is only operating on skb_shinfo(skb)->frags. If it is still trying to split such an skb and xmit'ing it on an interface without support for NETIF_F_FRAGLIST, then validate_xmit_skb() will try to linearize it. But this fails due to inconsistent information. And __pskb_pull_tail will trigger a BUG_ON after skb_copy_bits() returns an error. In case of entries in frag_list, just linearize the skb before operating on it with skb_split(). Reported-by: Felix Kaechele <felix@kaechele.ca> Fixes: c6c8fea29769 ("net: Add batman-adv meshing protocol") Signed-off-by: Sven Eckelmann <sven@narfation.org> Tested-by: Felix Kaechele <felix@kaechele.ca> Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions