Commit e24abee0 authored by Jan Beulich's avatar Jan Beulich Committed by Greg Kroah-Hartman
Browse files

xen-netback: correct success/error reporting for the SKB-with-fraglist case

[ Upstream commit 3ede7f84c7c21f93c5eac611d60eba3f2c765e0f ]

When re-entering the main loop of xenvif_tx_check_gop() a 2nd time, the
special considerations for the head of the SKB no longer apply. Don't
mistakenly report ERROR to the frontend for the first entry in the list,
even if - from all I can tell - this shouldn't matter much as the overall
transmit will need to be considered failed anyway.

Signed-off-by: default avatarJan Beulich <>
Reviewed-by: default avatarPaul Durrant <>
Signed-off-by: default avatarDavid S. Miller <>
Signed-off-by: default avatarSasha Levin <>
parent 323f0968
...@@ -994,7 +994,7 @@ check_frags: ...@@ -994,7 +994,7 @@ check_frags:
* the header's copy failed, and they are * the header's copy failed, and they are
* sharing a slot, send an error * sharing a slot, send an error
*/ */
if (i == 0 && sharedslot) if (i == 0 && !first_shinfo && sharedslot)
xenvif_idx_release(queue, pending_idx, xenvif_idx_release(queue, pending_idx,
else else
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment