On Mon, Aug 21, 2017 at 10:56 PM, Eric Dumazet wrote:
> Please do not top post.
Got it, thanks.
> On Mon, 2017-08-21 at 21:24 +0800, Tonghao Zhang wrote:
>> Thanks, yes this is a bug. I found this bug exists from 3.17~ 4.13.
>> The commit is d94e0417
>>
>
> This bug was there at the beginning o
Please do not top post.
On Mon, 2017-08-21 at 21:24 +0800, Tonghao Zhang wrote:
> Thanks, yes this is a bug. I found this bug exists from 3.17~ 4.13.
> The commit is d94e0417
>
This bug was there at the beginning of git tree.
> One question: should I send a patch for each kernel version bec
Thanks, yes this is a bug. I found this bug exists from 3.17~ 4.13.
The commit is d94e0417
One question: should I send a patch for each kernel version because
code conflicts ?
a patch for v4.12
a patch for v4.11
a patch for v4.10~v4.7
a patch for v4.6~v3.17
and
a patch for net-next, because
From: Tonghao Zhang
Date: Wed, 16 Aug 2017 20:02:45 -0700
> Because we remove the tcp_tw_recycle support in the commit
> 4396e46187c ('tcp: remove tcp_tw_recycle') and also delete
> the code 'af_ops->route_req' for sysctl_tw_recycle in tcp_conn_request.
> Now when we call the 'af_ops->route_req',
Because we remove the tcp_tw_recycle support in the commit
4396e46187c ('tcp: remove tcp_tw_recycle') and also delete
the code 'af_ops->route_req' for sysctl_tw_recycle in tcp_conn_request.
Now when we call the 'af_ops->route_req', the dist always is
NULL, and we remove the unnecessay check.
Signe
Because we remove the tcp_tw_recycle support in the commit
4396e46187c ('tcp: remove tcp_tw_recycle') and also delete
the code 'af_ops->route_req' for sysctl_tw_recycle in tcp_conn_request.
Now when we call the 'af_ops->route_req', the dist always is
NULL, and we remove the unnecessay check.
Signe
