From: Jakub Kicinski <kuba@kernel.org>
To: memoriaru@foxmail.com
Cc: netdev@vger.kernel.org, daniel@makrotopia.org, andrew@lunn.ch,
f.fainelli@gmail.com, olteanv@gmail.com, pabeni@redhat.com
Subject: Re: [PATCH net] net: dsa: mxl862xx: bound FDB dump walk with a read limit
Date: Thu, 19 Nov 2026 16:40:07 -0800 [thread overview]
Message-ID: <20261119164007.248c6d4c@kernel.org> (raw)
In-Reply-To: <tencent_50548A0CA0A2E93225C5F5DD2DA865400607@qq.com>
On Fri, 13 Nov 2026 20:45:08 +0800 memoriaru@foxmail.com wrote:
> If the firmware crashes or misbehaves mid-walk and never sets the last
> flag, the driver spins forever with RTNL held, blocking all netlink
> configuration and stack operations on the system.
Patch does not apply, not sure this is worth fixing tho.
I'm sure LLMs can point out 10,000 potentially unbounded loops
in the tree. And you don't even have HW to test this.
prev parent reply other threads:[~2026-11-20 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 12:45 [PATCH net] net: dsa: mxl862xx: bound FDB dump walk with a read limit memoriaru
2026-11-20 0:40 ` Jakub Kicinski [this message]
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=20261119164007.248c6d4c@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=f.fainelli@gmail.com \
--cc=memoriaru@foxmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
/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