From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Machon <daniel.machon@microchip.com>
Cc: <netdev-bot+sashiko@kernel.org>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@kernel.org>, <pabeni@redhat.com>,
<Steen.Hegelund@microchip.com>, <UNGLinuxDriver@microchip.com>,
<richardcochran@gmail.com>, <linux@armlinux.org.uk>,
<netdev@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <robert.marko@sartura.hr>,
<horatiu.vultur@microchip.com>,
<jensemil.schulzostergaard@microchip.com>
Subject: Re: [PATCH net-next v2 2/9] net: sparx5/lan969x: free the FDMA buffers on init errors and deinit
Date: Fri, 13 Nov 2026 19:14:00 -0800 [thread overview]
Message-ID: <20261113191400.2451b854@kernel.org> (raw)
In-Reply-To: <20261113075946.fptcvcesbmjlahpc@DEN-DL-M70577.microsemi.net>
On Fri, 13 Nov 2026 08:59:46 +0100 Daniel Machon wrote:
> > Would it work to set rx->page[fdma->dcb_index][fdma->db_index] = NULL
> > after page_pool_recycle_direct()? The poll loop would also need to
> > consume or refill that DB, or reuse the page in place, instead of
> > recycling the page while the DB still references it.
>
> I believe this issue is being addressed on net by Zhang Hewei [1]. I asked for
> changes on v3, but no response so far, so I see three options:
>
> 1) Wait for Zhang to eventually post a v4.
> 2) Send a follow-up fix for this, in case Zhang does not.
> 3) Incorporate the fix in v3 of this series.
>
> Either of these works for me, but as I dont know if a v4 is ever sent and how
> many respins that fix will require, it'll probably be fastest for me with 2) or
> 3)
>
> BTW. The high severity issues on patch #6 and #9 have the same root cause as
> this. So my response to those are the same as this.
>
> [1] https://lore.kernel.org/netdev/tencent_6BAC076E552C6F338052FC02794D9B28ED0A@qq.com/
> [2] https://lore.kernel.org/netdev/20261110105239.5olhrlwa3mck74f4@DEN-DL-M70577/
Looks like the author respun twice since your response.
Let's wait for the fixes to make it to net-next, v5 conflicts with
the changes you are making. Don't hesitate to post your own version
of the fixes if you prefer. I'd bet it's an LLM jokey blindly feeding
sashiko pre-existing issue reports into an LLM.
--
pw-bot: defer
next prev parent reply other threads:[~2026-11-14 3:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 14:31 [PATCH net-next v2 0/9] net: sparx5/lan969x: add support for changing the MTU Daniel Machon
2026-11-11 14:31 ` [PATCH net-next v2 1/9] net: sparx5/lan969x: stop the FDMA channels properly Daniel Machon
2026-11-12 17:33 ` netdev-bot+sashiko
2026-11-13 7:51 ` Daniel Machon
2026-11-14 3:16 ` Jakub Kicinski
2026-11-11 14:31 ` [PATCH net-next v2 2/9] net: sparx5/lan969x: free the FDMA buffers on init errors and deinit Daniel Machon
2026-11-12 17:33 ` netdev-bot+sashiko
2026-11-13 7:59 ` Daniel Machon
2026-11-14 3:14 ` Jakub Kicinski [this message]
2026-11-11 14:31 ` [PATCH net-next v2 3/9] net: sparx5/lan969x: add a helper for setting the MAC max frame length Daniel Machon
2026-11-11 14:31 ` [PATCH net-next v2 4/9] net: sparx5/lan969x: pass the FDMA rings to the init and alloc functions Daniel Machon
2026-11-11 14:31 ` [PATCH net-next v2 5/9] net: sparx5/lan969x: size the FDMA buffers from the port MTUs Daniel Machon
2026-11-11 14:31 ` [PATCH net-next v2 6/9] net: sparx5/lan969x: add support for resizing the FDMA buffers Daniel Machon
2026-11-12 17:33 ` netdev-bot+sashiko
2026-11-13 8:07 ` Daniel Machon
2026-11-11 14:31 ` [PATCH net-next v2 7/9] net: sparx5/lan969x: scale the queue watermarks with the MTU Daniel Machon
2026-11-11 14:31 ` [PATCH net-next v2 8/9] net: sparx5/lan969x: scale the TAS guard band " Daniel Machon
2026-11-12 17:33 ` netdev-bot+sashiko
2026-11-13 8:10 ` Daniel Machon
2026-11-11 14:31 ` [PATCH net-next v2 9/9] net: sparx5/lan969x: add support for changing " Daniel Machon
2026-11-12 17:33 ` netdev-bot+sashiko
2026-11-13 8:14 ` Daniel Machon
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=20261113191400.2451b854@kernel.org \
--to=kuba@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=jensemil.schulzostergaard@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=robert.marko@sartura.hr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.