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;
Subject: Re: [PATCH] tcp: Do not reset the icsk_ca_initialized in
 tcp_init_transfer.
To:     Neal Cardwell <ncardwell@google.com>,
        Eric Dumazet <edumazet@google.com>
Cc:     David Miller <davem@davemloft.net>,
        Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
        David Ahern <dsahern@kernel.org>,
        Jakub Kicinski <kuba@kernel.org>,
        Alexei Starovoitov <ast@kernel.org>,
        Daniel Borkmann <daniel@iogearbox.net>,
        Andrii Nakryiko <andrii@kernel.org>,
        Martin KaFai Lau <kafai@fb.com>,
        Song Liu <songliubraving@fb.com>,
        John Fastabend <john.fastabend@gmail.com>, kpsingh@kernel.org,
        netdev <netdev@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
        linux-kernel-mentees@lists.linuxfoundation.org,
        syzbot+f1e24a0594d4e3a895d3@syzkaller.appspotmail.com,
        Yuchung Cheng <ycheng@google.com>
References: <20210628144908.881499-1-phind.uet@gmail.com>
 <CANn89iJ6M2WFS3B+sSOysekScUFmO9q5YHxgHGsbozbvkW9ivg@mail.gmail.com>
 <79490158-e6d1-aabf-64aa-154b71205c74@gmail.com>
 <CADVnQy=Q9W=Vxu81ctPLx08D=ALnHBXGr0c4BLtQGxwQE+yjRg@mail.gmail.com>
 <ee5ef69e-ee3f-1df0-2033-5adc06a46b9c@gmail.com>
 <CADVnQynqMQhO4cBON=xUCkne9-E1hze3naMZZ8tQ-a0k71kh8g@mail.gmail.com>
 <205F52AB-4A5B-4953-B97E-17E7CACBBCD8@gmail.com>
 <CANn89iJbquZ=tVBRg7JNR8pB106UY4Xvi7zkPVn0Uov9sj8akg@mail.gmail.com>
 <1786BBEE-9C7B-45B2-B451-F535ABB804EF@gmail.com>
 <CANn89iK4Qwf0ezWac3Cn1xWN_Hw+-QL-+H8YmDm4cZP=FH+MTQ@mail.gmail.com>
 <CADVnQyk9maCc+tJ4-b6kufcBES9+Y2KpHPZadXssoVWX=Xr1Vw@mail.gmail.com>
From:   Phi Nguyen <phind.uet@gmail.com>
Message-ID: <30527e25-dd66-da7a-7344-494b4539abf7@gmail.com>
Date:   Thu, 1 Jul 2021 02:25:27 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CADVnQyk9maCc+tJ4-b6kufcBES9+Y2KpHPZadXssoVWX=Xr1Vw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 6/29/2021 11:59 PM, Neal Cardwell wrote:
>    On Tue, Jun 29, 2021 at 8:58 AM Eric Dumazet <edumazet@google.com> wrote:
>  From my perspective, the bug was introduced when that 8919a9b31eb4
> commit introduced icsk_ca_initialized and set icsk_ca_initialized to 0
> in tcp_init_transfer(), missing the possibility that a process could
> call setsockopt(TCP_CONGESTION)  in state TCP_SYN_SENT (i.e. after the
> connect() or TFO open sendmsg()), which would call
> tcp_init_congestion_control(). The 8919a9b31eb4 commit did not intend
> to reset any initialization that the user had already explicitly made;
> it just missed the possibility of that particular sequence (which
> syzkaller managed to find!).
> 
>> Although I am not sure what happens at accept() time when the listener
>> socket is cloned.
> 
> It seems that for listener sockets, they cannot initialize their CC
> module state, because there is no way for them to reach
> tcp_init_congestion_control(), since:
> 
> (a) tcp_set_congestion_control() -> tcp_reinit_congestion_control()
> will not call tcp_init_congestion_control() on a socket in CLOSE or
> LISTEN
> 
> (b) tcp_init_transfer() -> tcp_init_congestion_control() can only
> happen for established sockets and successful TFO SYN_RECV sockets
Is this what was mentioned in this commit ce69e563b325(tcp: make sure 
listeners don't initialize congestion-control state)

> --
> [PATCH] tcp: fix tcp_init_transfer() to not reset icsk_ca_initialized
> 
> This commit fixes a bug (found by syzkaller) that could cause spurious
> double-initializations for congestion control modules, which could cause memory
> leaks orother problems for congestion control modules (like CDG) that allocate
> memory in their init functions.
> 
> The buggy scenario constructed by syzkaller was something like:
> 
> (1) create a TCP socket
> (2) initiate a TFO connect via sendto()
> (3) while socket is in TCP_SYN_SENT, call setsockopt(TCP_CONGESTION),
>      which calls:
>         tcp_set_congestion_control() ->
>           tcp_reinit_congestion_control() ->
>             tcp_init_congestion_control()
> (4) receive ACK, connection is established, call tcp_init_transfer(),
>      set icsk_ca_initialized=0 (without first calling cc->release()),
>      call tcp_init_congestion_control() again.
> 
> Note that in this sequence tcp_init_congestion_control() is called twice
> without a cc->release() call in between. Thus, for CC modules that allocate
> memory in their init() function, e.g, CDG, a memory leak may occur. The
> syzkaller tool managed to find a reproducer that triggered such a leak in CDG.
> 
> The bug was introduced when that 8919a9b31eb4 commit introduced
> icsk_ca_initialized and set icsk_ca_initialized to 0 in tcp_init_transfer(),
> missing the possibility for a sequence like the one above, where a process
> could call setsockopt(TCP_CONGESTION) in state TCP_SYN_SENT (i.e. after the
> connect() or TFO open sendmsg()), which would call
> tcp_init_congestion_control(). The 8919a9b31eb4 commit did not intend to reset
> any initialization that the user had already explicitly made; it just missed
> the possibility of that particular sequence (which syzkaller managed to find).

Could I use your commit message when I resubmit patch?

Thank you.