[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220120194614.379f5f30@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Thu, 20 Jan 2022 19:46:14 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: ycaibb <ycaibb@...il.com>
Cc: edumazet@...gle.com, davem@...emloft.net, yoshfuji@...ux-ipv6.org,
dsahern@...nel.org, ast@...nel.org, daniel@...earbox.net,
andrii@...nel.org, kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH] ipv4: fix lock leaks
On Fri, 21 Jan 2022 11:11:08 +0800 ycaibb wrote:
> From: Ryan Cai <ycaibb@...il.com>
>
> In methods listening_get_first and listening_get_first in tcp_ipv4.c,
> there are lock leaks when seq_sk_match returns true.
This is on purpose, please read the code carefully and try to test
your patches.
Powered by blists - more mailing lists