From: Jakub Kicinski <kuba@kernel.org>
To: Martino Dell'Ambrogio <tillo@tillo.ch>
Cc: netdev@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: sfp: quirk support for XGS-PON ONT sticks with unclean EEPROMs
Date: Mon, 20 Jul 2026 17:31:56 -0700 [thread overview]
Message-ID: <20260720173156.41189431@kernel.org> (raw)
In-Reply-To: <20260705185440.136496-1-tillo@tillo.ch>
On Sun, 5 Jul 2026 20:54:37 +0200 Martino Dell'Ambrogio wrote:
> Some clone XGS-PON ONT sticks ship EEPROMs where the vendor PN field is
> filled with non-printable garbage past the legitimate string instead of
> the SFF-8472 mandated space padding. sfp_strlen() then can't trim the
> field, the exact-length check in sfp_match() rejects the quirk entry
> before the string comparison runs, and the quirk silently never applies
> — so the kernel honors the module's spurious TX_FAULT and eventually
> disables it.
The netdev patch queue has overflown.
If these patches are still relevant you'll have to repost them.
prev parent reply other threads:[~2026-07-21 0:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 18:54 [PATCH net-next 0/2] net: sfp: quirk support for XGS-PON ONT sticks with unclean EEPROMs Martino Dell'Ambrogio
2026-07-05 18:54 ` [PATCH net-next 1/2] net: sfp: allow prefix matching in quirk lookup Martino Dell'Ambrogio
2026-07-06 7:28 ` Maxime Chevallier
2026-07-05 18:54 ` [PATCH net-next 2/2] net: sfp: add quirks for OEM XGSPONST2001 and FS XGS-SFP-ONT-MACI Martino Dell'Ambrogio
2026-07-06 7:29 ` Maxime Chevallier
2026-07-21 0:31 ` 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=20260720173156.41189431@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tillo@tillo.ch \
/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