All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Max Kellermann <max.kellermann@ionos.com>
Cc: stable@vger.kernel.org, kuba@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: 6.18.45 regression with bnxt_en due to uninitialized RX page size
Date: Thu, 20 Aug 2026 13:21:33 +0200	[thread overview]
Message-ID: <2026082001-plunging-coroner-7128@gregkh> (raw)
In-Reply-To: <CAKPOu+-x_QPgp7gvApKNxd=aAONgNUmQQMbiLKwQghWd6u7Y=A@mail.gmail.com>

On Thu, Aug 20, 2026 at 09:44:06AM +0200, Max Kellermann wrote:
> Hi,
> 
> after updating our servers to 6.18.45, the bnxt_en NICs would fail to
> initialize:
> 
>  page_pool_create_percpu() gave up with errno -22
>  bnxt_en 0000:c4:00.0 eno12399np0: bnxt_alloc_mem err: ffffffea
> 
> The regression appears to have been introduced by the backport of
> ad9ffc61fafeb ("eth: bnxt: support qcfg provided rx page size"). It
> obtains rx_page_size from the per-queue configuration:
> 
>  rxr->rx_page_size = rxq->qcfg.rx_page_size;
> 
> The bnxt_en driver installs queue_mgmt_ops only when
> BNXT_SUPPORTS_QUEUE_API() is true. On some NICs (like ours),
> ndo_default_qcfg is never called and rxq->qcfg.rx_page_size remains
> zero, leading to bnxt_alloc_rx_page_pool() failure with -EINVAL.
> 
> This was fixed in master by:
> 
>  1410c7416dc3 ("eth: bnxt: always set the queue mgmt ops")
>  3cf48c04966e ("eth: bnxt: make sure we populate the qcfg defaults on
> old FW/HW")
> 
> After cherry-picking these two commits on top of 6.18.45, the error
> disappeared. I suggest backporting them.

Thanks for the info, I had seen that the last commit above was marked as
"fixing" the issue, but I had missed the previous one was required to
make it work.  Both now queued up.

greg k-h

      reply	other threads:[~2026-08-20 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  7:44 6.18.45 regression with bnxt_en due to uninitialized RX page size Max Kellermann
2026-08-20 11:21 ` Greg KH [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=2026082001-plunging-coroner-7128@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max.kellermann@ionos.com \
    --cc=netdev@vger.kernel.org \
    --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 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.