From: Jakub Kicinski <kuba@kernel.org>
To: lukasz.majewski@mailbox.org
Cc: Jakub Kicinski <kuba@kernel.org>,
festevam@gmail.com, linux-arm-kernel@lists.infradead.org,
s.hauer@pengutronix.de, kernel@pengutronix.de, horms@kernel.org,
shawnguo@kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, wahrenst@gmx.net, pabeni@redhat.com,
davem@davemloft.net, netdev@vger.kernel.org,
richardcochran@gmail.com, edumazet@google.com,
andrew+netdev@lunn.ch, robh@kernel.org, krzk+dt@kernel.org,
andrew@lunn.ch
Subject: Re: [net-next,v20,3/7] net: mtip: Add buffers management functions to the L2 switch driver
Date: Tue, 27 Jan 2026 18:25:54 -0800 [thread overview]
Message-ID: <20260128022554.4151421-1-kuba@kernel.org> (raw)
In-Reply-To: <20260126103400.1683125-4-lukasz.majewski@mailbox.org>
This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
For local reproduction steps see https://netdev-ai.bots.linux.dev/ai-local.html
---
net: mtip: Add buffers management functions to the L2 switch driver
This patch adds buffer management functions for the MTIP L2 switch
driver, implementing mtip_free_buffers(), mtip_create_page_pool(), and
mtip_alloc_buffers() for RX page pool and TX bounce buffer handling.
> diff --git a/drivers/net/ethernet/freescale/mtipsw/mtipl2sw.c b/drivers/net/ethernet/freescale/mtipsw/mtipl2sw.c
> index 03c5163d6508..9c21a3d29c1c 100644
> --- a/drivers/net/ethernet/freescale/mtipsw/mtipl2sw.c
> +++ b/drivers/net/ethernet/freescale/mtipsw/mtipl2sw.c
> @@ -888,11 +888,96 @@ static void mtip_get_drvinfo(struct net_device *dev,
>
> static void mtip_free_buffers(struct net_device *dev)
> {
> + struct mtip_ndev_priv *priv = netdev_priv(dev);
> + struct switch_enet_private *fep = priv->fep;
> + int i;
> +
> + for (i = 0; i < RX_RING_SIZE; i++) {
> + page_pool_put_full_page(fep->page_pool,
> + fep->page[i], false);
Can fep->page[i] be NULL here? When mtip_alloc_buffers() fails partway
through the RX allocation loop, it calls mtip_free_buffers() via the
error path. At that point, only some fep->page[] entries have been
allocated - the rest remain NULL from the kzalloc initialization.
The call chain page_pool_put_full_page()->page_pool_put_netmem()->
page_pool_unref_and_test()->page_pool_unref_netmem()->
netmem_get_pp_ref_count_ref() will attempt to access &NULL->pp_ref_count
when passed a NULL page, causing a NULL pointer dereference.
Should there be a NULL check before calling page_pool_put_full_page()?
> + fep->page[i] = NULL;
> + }
> +
> + page_pool_destroy(fep->page_pool);
> + fep->page_pool = NULL;
> +
> + for (i = 0; i < TX_RING_SIZE; i++)
> + kfree(fep->tx_bounce[i]);
> }
[ ... ]
> +static int mtip_alloc_buffers(struct net_device *dev)
> +{
> + struct mtip_ndev_priv *priv = netdev_priv(dev);
> + struct switch_enet_private *fep = priv->fep;
> + struct cbd_t *bdp;
> + struct page *page;
> + int i, ret;
> +
> + ret = mtip_create_page_pool(fep, RX_RING_SIZE);
> + if (ret < 0) {
> + dev_err(&fep->pdev->dev, "Failed to create page pool\n");
> + return ret;
> + }
> +
> + bdp = fep->rx_bd_base;
> + for (i = 0; i < RX_RING_SIZE; i++) {
> + page = page_pool_dev_alloc_pages(fep->page_pool);
> + if (!page) {
> + dev_err(&fep->pdev->dev,
> + "Failed to allocate page for rx buffer\n");
> + goto err;
> + }
[ ... ]
> + err:
> + mtip_free_buffers(dev);
When this error path is taken, fep->page[] may contain NULL entries for
pages that were never allocated.
> + return -ENOMEM;
> }
next prev parent reply other threads:[~2026-01-28 2:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 10:33 [net-next v20 0/7] net: mtip: Add support for MTIP imx287 L2 switch driver Lukasz Majewski
2026-01-26 10:33 ` [net-next v20 1/7] dt-bindings: net: Add MTIP L2 switch description Lukasz Majewski
2026-01-26 10:33 ` [net-next v20 2/7] net: mtip: The L2 switch driver for imx287 Lukasz Majewski
2026-01-28 2:25 ` [net-next,v20,2/7] " Jakub Kicinski
2026-01-28 21:41 ` Łukasz Majewski
2026-01-28 22:00 ` Andrew Lunn
2026-01-28 22:47 ` Łukasz Majewski
2026-01-26 10:33 ` [net-next v20 3/7] net: mtip: Add buffers management functions to the L2 switch driver Lukasz Majewski
2026-01-28 2:25 ` Jakub Kicinski [this message]
2026-01-28 21:48 ` [net-next,v20,3/7] " Łukasz Majewski
2026-01-26 10:33 ` [net-next v20 4/7] net: mtip: Add net_device_ops " Lukasz Majewski
2026-01-28 2:25 ` [net-next,v20,4/7] " Jakub Kicinski
2026-01-28 21:55 ` Łukasz Majewski
2026-01-29 2:05 ` Jakub Kicinski
2026-01-26 10:33 ` [net-next v20 5/7] net: mtip: Add mtip_switch_{rx|tx} " Lukasz Majewski
2026-01-26 10:33 ` [net-next v20 6/7] net: mtip: Extend the L2 switch driver with management operations Lukasz Majewski
2026-01-26 10:34 ` [net-next v20 7/7] net: mtip: Extend the L2 switch driver for imx287 with bridge operations Lukasz Majewski
2026-01-28 2:26 ` [net-next,v20,7/7] " Jakub Kicinski
2026-01-28 22:58 ` Łukasz Majewski
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=20260128022554.4151421-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=horms@kernel.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.majewski@mailbox.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wahrenst@gmx.net \
/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