From: Mark Bloch <mbloch@nvidia.com>
To: kernel test robot <lkp@intel.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
linux-kernel@vger.kernel.org, Gal Pressman <gal@nvidia.com>,
Alexei Lazar <alazar@nvidia.com>
Subject: Re: [PATCH net 09/11] net/mlx5e: Update and set Xon/Xoff upon MTU set
Date: Sun, 24 Aug 2025 17:28:13 +0300 [thread overview]
Message-ID: <db2de992-bd46-487e-a62a-8bce50e75a23@nvidia.com> (raw)
In-Reply-To: <202508242120.QljNCAgz-lkp@intel.com>
On 24/08/2025 16:54, kernel test robot wrote:
> Hi Mark,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on ec79003c5f9d2c7f9576fc69b8dbda80305cbe3a]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Mark-Bloch/net-mlx5-HWS-Fix-memory-leak-in-hws_pool_buddy_init-error-path/20250824-164938
> base: ec79003c5f9d2c7f9576fc69b8dbda80305cbe3a
> patch link: https://lore.kernel.org/r/20250824083944.523858-10-mbloch%40nvidia.com
> patch subject: [PATCH net 09/11] net/mlx5e: Update and set Xon/Xoff upon MTU set
> config: um-randconfig-002-20250824 (https://download.01.org/0day-ci/archive/20250824/202508242120.QljNCAgz-lkp@intel.com/config)
> compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project d26ea02060b1c9db751d188b2edb0059a9eb273d)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250824/202508242120.QljNCAgz-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202508242120.QljNCAgz-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> In file included from drivers/net/ethernet/mellanox/mlx5/core/en_main.c:34:
> In file included from include/net/tc_act/tc_gact.h:5:
> In file included from include/net/act_api.h:10:
> In file included from include/net/flow_offload.h:6:
> In file included from include/linux/netlink.h:7:
> In file included from include/linux/skbuff.h:17:
> In file included from include/linux/bvec.h:10:
> In file included from include/linux/highmem.h:12:
> In file included from include/linux/hardirq.h:11:
> In file included from arch/um/include/asm/hardirq.h:5:
> In file included from include/asm-generic/hardirq.h:17:
> In file included from include/linux/irq.h:20:
> In file included from include/linux/io.h:12:
> In file included from arch/um/include/asm/io.h:24:
> include/asm-generic/io.h:1175:55: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
> 1175 | return (port > MMIO_UPPER_LIMIT) ? NULL : PCI_IOBASE + port;
> | ~~~~~~~~~~ ^
> In file included from drivers/net/ethernet/mellanox/mlx5/core/en_main.c:52:
>>> drivers/net/ethernet/mellanox/mlx5/core/en/port_buffer.h:79:12: warning: declaration of 'struct ieee_pfc' will not be visible outside of this function [-Wvisibility]
> 79 | struct ieee_pfc *pfc,
> | ^
> 2 warnings generated.
It seems net/dcbnl.h is only included (via linux/netdevice.h)
if CONFIG_DCB is set. We've tested only by not setting
CONFIG_MLX5_CORE_EN_DCB but left CONFIG_DCB set so it was missed.
Will fix.
Mark
>
>
> vim +79 drivers/net/ethernet/mellanox/mlx5/core/en/port_buffer.h
>
> 68
> 69 #ifdef CONFIG_MLX5_CORE_EN_DCB
> 70 int mlx5e_port_manual_buffer_config(struct mlx5e_priv *priv,
> 71 u32 change, unsigned int mtu,
> 72 struct ieee_pfc *pfc,
> 73 u32 *buffer_size,
> 74 u8 *prio2buffer);
> 75 #else
> 76 static inline int
> 77 mlx5e_port_manual_buffer_config(struct mlx5e_priv *priv,
> 78 u32 change, unsigned int mtu,
> > 79 struct ieee_pfc *pfc,
> 80 u32 *buffer_size,
> 81 u8 *prio2buffer)
> 82 {
> 83 return 0;
> 84 }
> 85 #endif
> 86
>
next prev parent reply other threads:[~2025-08-24 14:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 8:39 [PATCH net 00/11] mlx5 misc fixes 2025-08-24 Mark Bloch
2025-08-24 8:39 ` [PATCH net 01/11] net/mlx5: HWS, Fix memory leak in hws_pool_buddy_init error path Mark Bloch
2025-08-24 8:39 ` [PATCH net 02/11] net/mlx5: HWS, Fix memory leak in hws_action_get_shared_stc_nic error flow Mark Bloch
2025-08-24 8:39 ` [PATCH net 03/11] net/mlx5: HWS, Fix uninitialized variables in mlx5hws_pat_calc_nop " Mark Bloch
2025-08-24 8:39 ` [PATCH net 04/11] net/mlx5: HWS, Fix pattern destruction in mlx5hws_pat_get_pattern error path Mark Bloch
2025-08-24 8:39 ` [PATCH net 05/11] net/mlx5: Reload auxiliary drivers on fw_activate Mark Bloch
2025-08-24 8:39 ` [PATCH net 06/11] net/mlx5: Fix lockdep assertion on sync reset unload event Mark Bloch
2025-08-24 8:39 ` [PATCH net 07/11] net/mlx5: Nack sync reset when SFs are present Mark Bloch
2025-08-24 8:39 ` [PATCH net 08/11] net/mlx5: Prevent flow steering mode changes in switchdev mode Mark Bloch
2025-08-24 8:39 ` [PATCH net 09/11] net/mlx5e: Update and set Xon/Xoff upon MTU set Mark Bloch
2025-08-24 13:54 ` kernel test robot
2025-08-24 14:28 ` Mark Bloch [this message]
2025-08-24 8:39 ` [PATCH net 10/11] net/mlx5e: Update and set Xon/Xoff upon port speed set Mark Bloch
2025-08-24 8:39 ` [PATCH net 11/11] net/mlx5e: Set local Xoff after FW update Mark Bloch
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=db2de992-bd46-487e-a62a-8bce50e75a23@nvidia.com \
--to=mbloch@nvidia.com \
--cc=alazar@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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
all inboxes | Powered by JetHome®