diff options
| author | Juergen Gross <jgross@suse.com> | 2018-12-18 16:06:19 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-01-13 10:05:28 +0100 |
| commit | c986a25496f578a5d3422b94d45ab661d904158f (patch) | |
| tree | a26d8a7aa28f2fc92335b38e880ff1fb206299be /net/core/sock.c | |
| parent | 291d37f7c3571ba7764fc20291754767af53ea0e (diff) | |
xen/netfront: tolerate frags with no data
[ Upstream commit d81c5054a5d1d4999c7cdead7636b6cd4af83d36 ]
At least old Xen net backends seem to send frags with no real data
sometimes. In case such a fragment happens to occur with the frag limit
already reached the frontend will BUG currently even if this situation
is easily recoverable.
Modify the BUG_ON() condition accordingly.
Tested-by: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/core/sock.c')
0 files changed, 0 insertions, 0 deletions