summaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorJuergen Gross <jgross@suse.com>2021-11-30 10:36:12 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-12-22 11:32:52 +0300
commitbd926d189210cd1d5b4e618e45898053be6b4b3b (patch)
treeb370007fdd5b1bdeff65434c136657c1b791f1ce /Makefile
parent88449dbe6203c3a91cf1c39ea3032ad61a297bd7 (diff)
downloadlinux-bd926d189210cd1d5b4e618e45898053be6b4b3b.tar.xz
xen/netback: don't queue unlimited number of packages
commit be81992f9086b230623ae3ebbc85ecee4d00a3d3 upstream. In case a guest isn't consuming incoming network traffic as fast as it is coming in, xen-netback is buffering network packages in unlimited numbers today. This can result in host OOM situations. Commit f48da8b14d04ca8 ("xen-netback: fix unlimited guest Rx internal queue and carrier flapping") meant to introduce a mechanism to limit the amount of buffered data by stopping the Tx queue when reaching the data limit, but this doesn't work for cases like UDP. When hitting the limit don't queue further SKBs, but drop them instead. In order to be able to tell Rx packages have been dropped increment the rx_dropped statistics counter in this case. It should be noted that the old solution to continue queueing SKBs had the additional problem of an overflow of the 32-bit rx_queue_len value would result in intermittent Tx queue enabling. This is part of XSA-392 Fixes: f48da8b14d04ca8 ("xen-netback: fix unlimited guest Rx internal queue and carrier flapping") Signed-off-by: Juergen Gross <jgross@suse.com> Reviewed-by: Jan Beulich <jbeulich@suse.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions