On 7/2/19 8:27 PM, Tony Lu wrote:
> Hello Eric,
>
> We have applied that commit e358f4af19db ("tcp: tcp_fragment() should
> apply sane memory limits")
> as a hotpatch in production environment. We found that it will make
> tcp long connection reset during sending out packet w
Hello Eric,
We have applied that commit e358f4af19db ("tcp: tcp_fragment() should
apply sane memory limits")
as a hotpatch in production environment. We found that it will make
tcp long connection reset during sending out packet when applying
that commit.
From: Eric Dumazet
Date: Fri, 21 Jun 2019 06:09:55 -0700
> tcp_fragment() might be called for skbs in the write queue.
>
> Memory limits might have been exceeded because tcp_sendmsg() only
> checks limits at full skb (64KB) boundaries.
>
> Therefore, we need to make sure tcp_fragment() wont pun
> On Jun 21, 2019, at 6:11 AM, Eric Dumazet wrote:
>
> tcp_fragment() might be called for skbs in the write queue.
>
> Memory limits might have been exceeded because tcp_sendmsg() only
> checks limits at full skb (64KB) boundaries.
>
> Therefore, we need to make sure tcp_fragment() wont pun
tcp_fragment() might be called for skbs in the write queue.
Memory limits might have been exceeded because tcp_sendmsg() only
checks limits at full skb (64KB) boundaries.
Therefore, we need to make sure tcp_fragment() wont punish applications
that might have setup very low SO_SNDBUF values.
Fixe