mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: Jian Shen <shenjian15@huawei.com>,
	Jijie Shao <shaojijie@huawei.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] net: hns3: destroy the page pool if RX buffer allocation fails
Date: Fri, 6 Nov 2026 18:03:07 +0000	[thread overview]
Message-ID: <20261106180307.GM865646@horms.kernel.org> (raw)
In-Reply-To: <20261103100533.1310018-1-vulab@iscas.ac.cn>

On Tue, Nov 03, 2026 at 10:05:33AM +0000, Wentao Liang wrote:
> hns3_alloc_ring_memory() creates the page pool and then fills the RX
> ring with buffers from it. If filling the ring fails, the error path
> only frees the descriptors and the descriptor callbacks, so the page
> pool created a moment earlier is leaked.
> 
> The page pool is normally destroyed by hns3_fini_ring(), but
> hns3_init_all_ring() only cleans up the rings that were set up before
> the failing one, so the pool of the failing ring is never released.
> 
> Destroy the page pool on the buffer allocation failure path too.
> 
> Fixes: 93188e9642c3 ("net: hns3: support skb's frag page recycling based on page pool")
> Cc: stable@vger.kernel.org
> Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
>  drivers/net/ethernet/hisilicon/hns3/hns3_enet.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c b/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c
> index 47788be64be6..fe339ddc6379 100644
> --- a/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c
> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c
> @@ -5073,6 +5073,10 @@ static int hns3_alloc_ring_memory(struct hns3_enet_ring *ring)
>  
>  out_with_desc:
>  	hns3_free_desc(ring);
> +	if (ring->page_pool) {
> +		page_pool_destroy(ring->page_pool);
> +		ring->page_pool = NULL;
> +	}

The condition is not necessary as as page_pool_destroy is a no-op when
passed NULL. Please remove it to simplify the code-flow.

>  out_with_desc_cb:
>  	devm_kfree(ring_to_dev(ring), ring->desc_cb);
>  	ring->desc_cb = NULL;
> -- 
> 2.34.1

You will also need to answer the questions about providence posed by the
bot. Ideally in the patch description if you post a v2.

-- 
pw-bot: changes-requested

  parent reply	other threads:[~2026-11-06 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 10:05 Wentao Liang
2026-11-03 10:10 ` netdev-bot+sinfo
2026-11-03 10:25 ` Krzysztof Kozlowski
2026-11-06 18:03 ` Simon Horman [this message]
2026-11-07  6:40   ` Wentao Liang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261106180307.GM865646@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shaojijie@huawei.com \
    --cc=shenjian15@huawei.com \
    --cc=stable@vger.kernel.org \
    --cc=vulab@iscas.ac.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®