[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpVBrHy9-UP2ycHd0vXgtpfC1sVgJY8C+SMDoM98f3NVcQ@mail.gmail.com>
Date: Mon, 7 Oct 2019 22:58:33 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Maciej Żenczykowski <zenczykowski@...il.com>
Cc: Maciej Żenczykowski <maze@...gle.com>,
"David S . Miller" <davem@...emloft.net>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
Pablo Neira Ayuso <pablo@...filter.org>
Subject: Re: [PATCH 2/2] netfilter: revert "conntrack: silent a memory leak warning"
On Mon, Oct 7, 2019 at 10:35 PM Maciej Żenczykowski
<zenczykowski@...il.com> wrote:
>
> From: Maciej Żenczykowski <maze@...gle.com>
>
> This reverts commit 114aa35d06d4920c537b72f9fa935de5dd205260.
>
> By my understanding of kmemleak the reasoning for this patch
> is incorrect. If kmemleak couldn't handle rcu we'd have it
> reporting leaks all over the place. My belief is that this
> was instead papering over a real leak.
If you have this belief, please:
1. Explain in details why you believe it or what supports it. For
example, did you see any kernel memory continue growing?
2. You want to fix the comment right above __krealloc() before fixing
anything else.
Thanks.
Powered by blists - more mailing lists