Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp3092937pxb; Mon, 9 Nov 2020 02:16:37 -0800 (PST) X-Google-Smtp-Source: ABdhPJySEDOneMyMkB3Rknk2xHOcPcZEEduFtgac8UFGyXXqrGHXa6nhCx5qTnwJF5DMioiRKav8 X-Received: by 2002:a50:cd51:: with SMTP id d17mr14090705edj.93.1604916997329; Mon, 09 Nov 2020 02:16:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604916997; cv=none; d=google.com; s=arc-20160816; b=RWDnon4zyH8PmW4HoGiKok64nJU+6qybFA2ywSZr4kD8KVmMm4SXqytFIhKoPjWwHF tGkHPydS2nE73P29VAMA5asnds9IZ/85RmKWAmOXn4L8anVSb+PGvqO5zZX5JBgNzkBx s5g6iQJv3OSfxOZwOhcGFpTnuFmrO0Rmq7Mzo7gOmnkeymU/Kne3iQj+s8hG9h1pkEvg w/N8UtroxHmC16MBmCAfJXNz4ICzXk9gysqwTeYXH09PFfIZqI4BXlmW9ipzNORfcUJF IS2Opq5wa1yyVJCJ7ACjahJMmFgUiEPYaPnU/80vpOnqLqvFAblb00Oety8h2SjgHJjr FtvQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=hAwGYPPnIuHDRZIl3PvUHbi+LXtb00ihWQdJ/2gcJjM=; b=mTVDo6sYJQrGJiJ8YoH1ozlr/OMiXi07NKFRJlTekG6TeA33vJiSd/Z9FI3Gr/17EV knP/xN45/6GFPxVRTuQD804sOMwdxe1fOsozFJbPEXj1WbYEJZN/bJMKdDAQgBzXOXW8 Do8687Vly1c4RcRjKDhIEVgo3MLikI9wjobKhaY2es82phlVkWOQ3y6OKceTIJ8LHW5y pPmkVIpMpkJhHHY/Phd7tYTfwctV/A41+ngy0DuWZN/hjyc8gKeKVr4pfGK9ciYI3dkZ Xqmw2+OimKd2joOgHHsYyjO6Moj7R96ZLy3S3wyX/5ca+1O8wJIEC8rltHzne7BiRzAi +1vQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x14si6743352ejs.714.2020.11.09.02.16.14; Mon, 09 Nov 2020 02:16:37 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729037AbgKIKMp (ORCPT + 99 others); Mon, 9 Nov 2020 05:12:45 -0500 Received: from out30-131.freemail.mail.aliyun.com ([115.124.30.131]:53982 "EHLO out30-131.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726176AbgKIKMp (ORCPT ); Mon, 9 Nov 2020 05:12:45 -0500 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R231e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04400;MF=wenan.mao@linux.alibaba.com;NM=1;PH=DS;RN=8;SR=0;TI=SMTPD_---0UEhrQpj_1604916760; Received: from B-44NBMD6M-0121.local(mailfrom:wenan.mao@linux.alibaba.com fp:SMTPD_---0UEhrQpj_1604916760) by smtp.aliyun-inc.com(127.0.0.1); Mon, 09 Nov 2020 18:12:40 +0800 Subject: Re: [PATCH net v2] net: Update window_clamp if SOCK_RCVBUF is set To: Eric Dumazet Cc: David Miller , Alexey Kuznetsov , Hideaki YOSHIFUJI , Jakub Kicinski , netdev , LKML , kernel-janitors@vger.kernel.org References: <1604913614-19432-1-git-send-email-wenan.mao@linux.alibaba.com> <1604914417-24578-1-git-send-email-wenan.mao@linux.alibaba.com> From: Mao Wenan Message-ID: <3b92167c-201c-e85d-822d-06f0c9ac508c@linux.alibaba.com> Date: Mon, 9 Nov 2020 18:12:40 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.3.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2020/11/9 下午5:56, Eric Dumazet 写道: > On Mon, Nov 9, 2020 at 10:33 AM Mao Wenan wrote: >> >> When net.ipv4.tcp_syncookies=1 and syn flood is happened, >> cookie_v4_check or cookie_v6_check tries to redo what >> tcp_v4_send_synack or tcp_v6_send_synack did, >> rsk_window_clamp will be changed if SOCK_RCVBUF is set, >> which will make rcv_wscale is different, the client >> still operates with initial window scale and can overshot >> granted window, the client use the initial scale but local >> server use new scale to advertise window value, and session >> work abnormally. > > What is not working exactly ? > > Sending a 'big wscale' should not really matter, unless perhaps there > is a buggy stack at the remote end ? 1)in tcp_v4_send_synack, if SO_RCVBUF is set and tcp_full_space(sk)=65535, pass req->rsk_window_clamp=65535 to tcp_select_initial_window, rcv_wscale will be zero, and send to client, the client consider wscale is 0; 2)when ack is back from client, if there is no this patch, req->rsk_window_clamp is 0, and pass to tcp_select_initial_window, wscale will be 7, this new rcv_wscale is no way to advertise to client. 3)if server send rcv_wind to client with window=63, it consider the real window is 63*2^7=8064, but client consider the server window is only 63*2^0=63, it can't send big packet to server, and the send-q of client is full. > >> >> Signed-off-by: Mao Wenan >> --- >> v2: fix for ipv6. >> net/ipv4/syncookies.c | 4 ++++ >> net/ipv6/syncookies.c | 5 +++++ >> 2 files changed, 9 insertions(+) >> >> diff --git a/net/ipv4/syncookies.c b/net/ipv4/syncookies.c >> index 6ac473b..57ce317 100644 >> --- a/net/ipv4/syncookies.c >> +++ b/net/ipv4/syncookies.c >> @@ -427,6 +427,10 @@ struct sock *cookie_v4_check(struct sock *sk, struct sk_buff *skb) >> >> /* Try to redo what tcp_v4_send_synack did. */ >> req->rsk_window_clamp = tp->window_clamp ? :dst_metric(&rt->dst, RTAX_WINDOW); >> + /* limit the window selection if the user enforce a smaller rx buffer */ >> + if (sk->sk_userlocks & SOCK_RCVBUF_LOCK && >> + (req->rsk_window_clamp > tcp_full_space(sk) || req->rsk_window_clamp == 0)) >> + req->rsk_window_clamp = tcp_full_space(sk); > > This seems not needed to me. > > We call tcp_select_initial_window() with tcp_full_space(sk) passed as > the 2nd parameter. > > tcp_full_space(sk) will then apply : > > space = min(*window_clamp, space); if cookie_v4_check pass window_clamp=0 to tcp_select_initial_window, it will set window_clamp to max value. (*window_clamp) = (U16_MAX << TCP_MAX_WSCALE); but space will fetch from sysctl_rmem_max and sysctl_tcp_rmem[2] which is also big value. space = max_t(u32, space, sock_net(sk)->ipv4.sysctl_tcp_rmem[2]); space = max_t(u32, space, sysctl_rmem_max); Then,space = min(*window_clamp, space) is a big value, lead wscale to 7, is different from tcp_v4_send_synack. > > Please cook a packetdrill test to demonstrate what you are seeing ? > I have real environment and reproduce this case, this patch can fix that, i will try to use packetdrill with syn cookies and syn flood happen.