From: sashiko-bot@kernel.org
To: wei.fang@oss.nxp.com
Cc: imx@lists.linux.dev, Frank.Li@kernel.org
Subject: Re: [PATCH v2 net-next 02/14] net: enetc: extract common helpers for MAC hash filter configuration
Date: Fri, 03 Jul 2026 03:27:01 +0000 [thread overview]
Message-ID: <20260703032702.231E51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260702025714.456233-3-wei.fang@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Pre-existing logic bug: Fallback to hash-based filtering fails for exact match (EM) MAC addresses because the hash table is not populated.
--
commit 0373b31ab4e7a0beb8461d5ceb05e09d7d5b61ab
Author: Wei Fang <wei.fang@nxp.com>
Date: Thu Jul 2 02:57:02 2026 +0000
net: enetc: extract common helpers for MAC hash filter configuration
The patch extracts enetc_set_si_uc_hash_filter() and
enetc_set_si_mc_hash_filter() into enetc_pf_common.c. This allows sharing
the MAC hash filter configuration between ENETC v1 and v4 drivers, and
removes redundant hardware-specific functions.
> diff --git a/drivers/net/ethernet/freescale/enetc/enetc_pf.c b/drivers/net/ethernet/freescale/enetc/enetc_pf.c
> index a97d2e2dd07b7..db2a800a7aaf0 100644
> --- a/drivers/net/ethernet/freescale/enetc/enetc_pf.c
> +++ b/drivers/net/ethernet/freescale/enetc/enetc_pf.c
[ ... ]
> @@ -135,7 +108,7 @@ static void enetc_sync_mac_filters(struct enetc_pf *pf)
> if (em) {
> int err;
>
> - enetc_clear_mac_ht_flt(si, 0, UC);
> + enetc_set_si_uc_hash_filter(si, 0, 0);
>
> err = enetc_set_mac_flt_entry(si, pos, f->mac_addr,
> BIT(0));
> @@ -147,11 +120,15 @@ static void enetc_sync_mac_filters(struct enetc_pf *pf)
> err);
> }
>
> + bitmap_to_arr64(&hash, f->mac_hash_table,
> + ENETC_MADDR_HASH_TBL_SZ);
> /* hash table filter, clear EM filter for UC entries */
> - if (i == UC)
> + if (i == UC) {
> enetc_clear_mac_flt_entry(si, pos);
> -
> - enetc_set_mac_ht_flt(si, 0, i, *f->mac_hash_table);
> + enetc_set_si_uc_hash_filter(si, 0, hash);
[Severity: High]
This is a pre-existing issue, but does this fallback path actually work for
exact match MAC addresses?
In enetc_pf_set_rx_mode(), when configuring a single unicast MAC address,
enetc_add_mac_addr_em_filter() is called, but the hash table population is
explicitly skipped:
enetc_pf_set_rx_mode() {
...
em = (netdev_uc_count(ndev) == 1);
netdev_for_each_uc_addr(ha, ndev) {
if (em) {
enetc_add_mac_addr_em_filter(filter, ha->addr);
break;
}
enetc_add_mac_addr_ht_filter(filter, ha->addr);
}
...
}
Because of this, mac_hash_table remains empty for the EM filter.
If enetc_set_mac_flt_entry() fails in enetc_sync_mac_filters(), the driver
warns "fallback to HT filt" and falls through to this block. However, since
the hash table was never populated, the derived hash is 0.
Doesn't this result in programming an empty hash filter, which will silently
drop all packets for this intended MAC address instead of falling back to
hash-based filtering?
> + } else {
> + enetc_set_si_mc_hash_filter(si, 0, hash);
> + }
> }
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260702025714.456233-1-wei.fang@oss.nxp.com?part=2
next prev parent reply other threads:[~2026-07-03 3:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 2:57 [PATCH v2 net-next 00/14] net: enetc: cleanups and improvements wei.fang
2026-07-02 2:57 ` [PATCH v2 net-next 01/14] net: enetc: extract common helpers for MAC promiscuous mode setting wei.fang
2026-07-02 2:57 ` [PATCH v2 net-next 02/14] net: enetc: extract common helpers for MAC hash filter configuration wei.fang
2026-07-03 3:27 ` sashiko-bot [this message]
2026-07-03 7:02 ` Wei Fang (OSS)
2026-07-02 2:57 ` [PATCH v2 net-next 03/14] net: enetc: convert ndo_set_rx_mode() to ndo_set_rx_mode_async() wei.fang
2026-07-02 2:57 ` [PATCH v2 net-next 04/14] net: enetc: improve MAFT entry management with bitmap tracking wei.fang
2026-07-02 2:57 ` [PATCH v2 net-next 05/14] net: enetc: use PCI device name for debugfs directory wei.fang
2026-07-02 2:57 ` [PATCH v2 net-next 06/14] net: enetc: simplify enetc4_set_port_speed() wei.fang
2026-07-02 17:32 ` Maxime Chevallier
2026-07-03 3:27 ` sashiko-bot
2026-07-02 2:57 ` [PATCH v2 net-next 07/14] net: enetc: differentiate phylink capabilities for pseudo-MAC and standalone MAC wei.fang
2026-07-02 17:30 ` Maxime Chevallier
2026-07-03 3:27 ` sashiko-bot
2026-07-02 2:57 ` [PATCH v2 net-next 08/14] net: enetc: remove invalid code from enetc4_pl_mac_link_up() wei.fang
2026-07-02 17:35 ` Maxime Chevallier
2026-07-02 2:57 ` [PATCH v2 net-next 09/14] net: enetc: remove enetc4_set_default_si_vlan_promisc() wei.fang
2026-07-02 2:57 ` [PATCH v2 net-next 10/14] net: enetc: refactor SI VLAN promiscuous mode configuration wei.fang
2026-07-03 3:27 ` sashiko-bot
2026-07-02 2:57 ` [PATCH v2 net-next 11/14] net: enetc: move enetc_set_si_vlan_promisc() to enetc_pf_common.c wei.fang
2026-07-02 2:57 ` [PATCH v2 net-next 12/14] net: enetc: remove redundant num_vsi field from enetc_port_caps wei.fang
2026-07-02 2:57 ` [PATCH v2 net-next 13/14] net: enetc: use alloc_etherdev_mqs() to create netdev for VF driver wei.fang
2026-07-03 3:27 ` sashiko-bot
2026-07-02 2:57 ` [PATCH v2 net-next 14/14] net: enetc: use kzalloc_flex() for enetc_psfp_gate allocation wei.fang
2026-07-03 3:27 ` sashiko-bot
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=20260703032702.231E51F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=imx@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wei.fang@oss.nxp.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