diff options
| author | Eric Dumazet <edumazet@google.com> | 2017-02-02 20:40:08 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-02-03 16:23:57 -0500 |
| commit | 38ab52e8e1e2dd65f2d349f82553335813b638d2 (patch) | |
| tree | 659bcbc397163954d2845ef6f438996da8ee1412 /net/tipc/ib_media.c | |
| parent | 5226b7919641f285bf0f8db84deeb3920b160ec7 (diff) | |
tcp: clear pfmemalloc on outgoing skb
Josef Bacik diagnosed following problem :
I was seeing random disconnects while testing NBD over loopback.
This turned out to be because NBD sets pfmemalloc on it's socket,
however the receiving side is a user space application so does not
have pfmemalloc set on its socket. This means that
sk_filter_trim_cap will simply drop this packet, under the
assumption that the other side will simply retransmit. Well we do
retransmit, and then the packet is just dropped again for the same
reason.
It seems the better way to address this problem is to clear pfmemalloc
in the TCP transmit path. pfmemalloc strict control really makes sense
on the receive path.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Acked-by: Josef Bacik <jbacik@fb.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc/ib_media.c')
0 files changed, 0 insertions, 0 deletions