From: Matt Vollrath <tactii@gmail.com>
To: intel-wired-lan@lists.osuosl.org
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH iwl-net 3/3] e1000e: fix NETIF_F_RXALL buffer overrun
Date: Thu, 3 Sep 2026 12:00:53 -0400 [thread overview]
Message-ID: <eb208b80-4cf2-4c3b-90c7-f68520382cf6@gmail.com> (raw)
In-Reply-To: <20260902032913.661570-4-tactii@gmail.com>
On 9/1/26 23:29, Matt Vollrath wrote:
> When SBP is set, the card may deliver frames which would otherwise be
> filtered out by LPE being unset. This would allow the device to write
> up to 526 bytes beyond the skb's data allocation: over its own shinfo,
> and beyond. This bug is reachable only when MTU <= 1500 and
> NETIF_F_RXALL is set ("ethtool -K <dev> rx-all on").
>
> Ensure that buffers are large enough for an entire 2048 byte chunk when
> NETIF_F_RXALL is set. Do this by moving final rx_buffer_len
> determination to one place, right before RCTL.BSIZE is determined. This
> will correctly re-evaluate every time the adapter is configured, not
> just on MTU change.
>
> Signed-off-by: Matt Vollrath <tactii@gmail.com>
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
> Assisted-by: Claude:claude-5-fable
> Fixes: cf955e6c96cb ("e1000e: Support RXALL feature flag.")
> Cc: stable@vger.kernel.org
> ---
> drivers/net/ethernet/intel/e1000e/netdev.c | 53 +++++++++++++---------
> 1 file changed, 32 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c b/drivers/net/ethernet/intel/e1000e/netdev.c
> index 063fc8cd2673..80d5a0010df8 100644
> --- a/drivers/net/ethernet/intel/e1000e/netdev.c
> +++ b/drivers/net/ethernet/intel/e1000e/netdev.c
> @@ -3036,6 +3036,33 @@ static void e1000_configure_tx(struct e1000_adapter *adapter)
> #define PAGE_USE_COUNT(S) (((S) >> PAGE_SHIFT) + \
> (((S) & (PAGE_SIZE - 1)) ? 1 : 0))
>
> +/**
> + * e1000_set_rx_buffer_len - determine the Rx buffer size
> + * @adapter: Board private structure
> + **/
> +static void e1000_set_rx_buffer_len(struct e1000_adapter *adapter)
> +{
> + struct net_device *netdev = adapter->netdev;
> + u32 max_frame = adapter->max_frame_size;
> +
> + /* NOTE: netdev_alloc_skb reserves 16 bytes, and typically NET_IP_ALIGN
> + * means we reserve 2 more, this pushes us to allocate from the next
> + * larger slab size.
> + * i.e. RXBUFFER_2048 --> size-4096 slab
> + * However with the new *_jumbo_rx* routines, jumbo receives will use
> + * fragmented skbs
> + */
> + if (max_frame <= 2048)
> + adapter->rx_buffer_len = 2048;
> + else
> + adapter->rx_buffer_len = 4096;
> +
> + /* adjust allocation if LPE protects us, and we aren't using SBP */
> + if (max_frame <= (VLAN_ETH_FRAME_LEN + ETH_FCS_LEN) &&
> + !(netdev->features & NETIF_F_RXALL))
> + adapter->rx_buffer_len = VLAN_ETH_FRAME_LEN + ETH_FCS_LEN;
> +}
> +
> /**
> * e1000_setup_rctl - configure the receive control registers
> * @adapter: Board private structure
> @@ -3102,6 +3129,8 @@ static void e1000_setup_rctl(struct e1000_adapter *adapter)
> e1e_wphy(hw, 22, phy_data);
> }
>
> + e1000_set_rx_buffer_len(adapter);
> +
> /* Setup buffer sizes */
> rctl &= ~E1000_RCTL_SZ_4096;
> rctl |= E1000_RCTL_BSEX;
> @@ -6087,30 +6116,12 @@ static int e1000_change_mtu(struct net_device *netdev, int new_mtu)
>
> pm_runtime_get_sync(netdev->dev.parent);
>
> - if (netif_running(netdev))
> + if (netif_running(netdev)) {
I see now that I should not have collapsed this to one netif_running check.
> e1000e_down(adapter, true);
> -
> - /* NOTE: netdev_alloc_skb reserves 16 bytes, and typically NET_IP_ALIGN
> - * means we reserve 2 more, this pushes us to allocate from the next
> - * larger slab size.
> - * i.e. RXBUFFER_2048 --> size-4096 slab
> - * However with the new *_jumbo_rx* routines, jumbo receives will use
> - * fragmented skbs
> - */
> -
> - if (max_frame <= 2048)
> - adapter->rx_buffer_len = 2048;
> - else
> - adapter->rx_buffer_len = 4096;
> -
> - /* adjust allocation if LPE protects us, and we aren't using SBP */
> - if (max_frame <= (VLAN_ETH_FRAME_LEN + ETH_FCS_LEN))
> - adapter->rx_buffer_len = VLAN_ETH_FRAME_LEN + ETH_FCS_LEN;
> -
> - if (netif_running(netdev))
> e1000e_up(adapter);
> - else
> + } else {
> e1000e_reset(adapter);
> + }
>
> pm_runtime_put_sync(netdev->dev.parent);
>
prev parent reply other threads:[~2026-09-03 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 3:29 [PATCH iwl-net 0/3] e1000e: fix Rx bugs Matt Vollrath
2026-09-02 3:29 ` [PATCH iwl-net 1/3] e1000e: fix Rx skb DMA map error sentinel Matt Vollrath
2026-09-02 3:29 ` [PATCH iwl-net 2/3] e1000e: fix ps_pages " Matt Vollrath
2026-09-02 3:29 ` [PATCH iwl-net 3/3] e1000e: fix NETIF_F_RXALL buffer overrun Matt Vollrath
2026-09-03 16:00 ` Matt Vollrath [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=eb208b80-4cf2-4c3b-90c7-f68520382cf6@gmail.com \
--to=tactii@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=stable@vger.kernel.org \
/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