From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: <darren.worrall@shopify.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: <intel-wired-lan@lists.osuosl.org>,
Eric Dumazet <edumazet@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Tatyana Nikolova <tatyana.e.nikolova@intel.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, Madhu Chittim <madhu.chittim@intel.com>,
Joshua Hay <joshua.a.hay@intel.com>
Subject: Re: [PATCH iwl-net] idpf: select AUXILIARY_BUS to fix link failure
Date: Thu, 12 Nov 2026 11:30:00 +0100 [thread overview]
Message-ID: <2432bda7-8867-44ff-bd86-1897995d3acb@intel.com> (raw)
In-Reply-To: <20261111-idpf-auxiliary-bus-v1-1-e76b940fc929@shopify.com>
On 11/11/26 8:31 PM, Darren Worrall via B4 Relay wrote:
> From: Darren Worrall <darren.worrall@shopify.com>
>
> The build can currently fail with
>
> ld: vmlinux.o: in function `idpf_plug_vport_aux_dev':
> drivers/net/ethernet/intel/idpf/idpf_idc.c:82: undefined reference to `auxiliary_device_init'
> ld: drivers/net/ethernet/intel/idpf/idpf_idc.c:86: undefined reference to `__auxiliary_device_add'
> ld: vmlinux.o: in function `idpf_plug_core_aux_dev':
> drivers/net/ethernet/intel/idpf/idpf_idc.c:223: undefined reference to `auxiliary_device_init'
> ld: drivers/net/ethernet/intel/idpf/idpf_idc.c:227: undefined reference to `__auxiliary_device_add'
>
> if IDPF is enabled but no other driver pulls in AUXILIARY_BUS. We hit
> this building a minimal kernel for hosts with IDPF NICs. It can be
> reproduced on x86_64 from allnoconfig by enabling PCI, PCI_MSI, NET,
> NETDEVICES, ETHERNET, NET_VENDOR_INTEL and IDPF.
>
> Select AUXILIARY_BUS in IDPF, as ICE and I40E already do. The same
> link failure was fixed for BNGE in commit d7065436e8a0 ("net: bnge: add
> AUXILIARY_BUS to Kconfig dependencies").
>
> Build-tested with that configuration on net-queue (dev-queue,
> 34a70a40c954) and on mainline (067c5c24cef2): vmlinux fails to link
> without this patch and links with it. Boot-tested on bare metal (AMD
> EPYC) with a Google Cloud IDPF NIC, using a 6.18.60 kernel carrying the
> same change and IDPF built in: idpf probes the NIC and its link comes
> up.
>
> Fixes: f4312e6bfa2a ("idpf: implement core RDMA auxiliary dev create, init, and destroy")
> Cc: stable@vger.kernel.org # 6.17+
> Signed-off-by: Darren Worrall <darren.worrall@shopify.com>
Thank you!
Acked-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> ---
> The link failure was diagnosed, this patch drafted and the tests above
> run with the help of an AI coding assistant. I reviewed the patch and
> the test results.
> ---
> drivers/net/ethernet/intel/idpf/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/intel/idpf/Kconfig b/drivers/net/ethernet/intel/idpf/Kconfig
> index 586df3a4af..6b59173e0d 100644
> --- a/drivers/net/ethernet/intel/idpf/Kconfig
> +++ b/drivers/net/ethernet/intel/idpf/Kconfig
> @@ -5,6 +5,7 @@ config IDPF
> tristate "Intel(R) Infrastructure Data Path Function Support"
> depends on PCI_MSI
> depends on PTP_1588_CLOCK_OPTIONAL
> + select AUXILIARY_BUS
> select DIMLIB
> select LIBIE_CP
> select LIBETH_XDP
>
> ---
> base-commit: 34a70a40c954fb8044ecd124840a2c38cd3aa4cc
> change-id: 20261111-idpf-auxiliary-bus-c0058e27cd9d
>
> Best regards,
> --
> Darren Worrall <darren.worrall@shopify.com>
>
>
prev parent reply other threads:[~2026-11-12 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 19:31 [PATCH iwl-net] idpf: select AUXILIARY_BUS to fix link failure Darren Worrall via B4 Relay
2026-11-12 10:30 ` Przemek Kitszel [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=2432bda7-8867-44ff-bd86-1897995d3acb@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=darren.worrall@shopify.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tatyana.e.nikolova@intel.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