[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240426160711.4fd99586@kernel.org>
Date: Fri, 26 Apr 2024 16:07:11 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Mina Almasry <almasrymina@...gle.com>
Cc: Dragos Tatulea <dtatulea@...dia.com>, "jacob.e.keller@...el.com"
<jacob.e.keller@...el.com>, "edumazet@...gle.com" <edumazet@...gle.com>,
"davem@...emloft.net" <davem@...emloft.net>, "pabeni@...hat.com"
<pabeni@...hat.com>, "ilias.apalodimas@...aro.org"
<ilias.apalodimas@...aro.org>, Jianbo Liu <jianbol@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] net: Fix one page_pool page leak from
skb_frag_unref
On Wed, 24 Apr 2024 15:08:42 -0700 Mina Almasry wrote:
> I'm unable to repro this issue. Do you need to do anything special? Or
> is 1 flow that hits skb_segment() good enough?
At some point we may want to start writing unit tests to make sure
we don't regress the 5 corner cases we found previously.. ;)
Should be easy to operate on skbs under kunit.
Powered by blists - more mailing lists