From: kernel test robot <lkp@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: drivers/net/ethernet/mellanox/mlx5/core/en/qos.c:364:40: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Mon, 18 Sep 2023 06:24:10 +0800 [thread overview]
Message-ID: <202309180636.BDozYbf4-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: e789286468a9ea7acb5aae09a11bdfc7d46874ec
commit: d636fc5dd692c8f4e00ae6e0359c0eceeb5d9bdb net: sched: add rcu annotations around qdisc->qdisc_sleeping
date: 3 months ago
config: i386-randconfig-063-20230918 (https://download.01.org/0day-ci/archive/20230918/202309180636.BDozYbf4-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230918/202309180636.BDozYbf4-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/202309180636.BDozYbf4-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/mellanox/mlx5/core/en/qos.c:364:40: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct Qdisc *qdisc @@ got struct Qdisc [noderef] __rcu *qdisc_sleeping @@
drivers/net/ethernet/mellanox/mlx5/core/en/qos.c:364:40: sparse: expected struct Qdisc *qdisc
drivers/net/ethernet/mellanox/mlx5/core/en/qos.c:364:40: sparse: got struct Qdisc [noderef] __rcu *qdisc_sleeping
vim +364 drivers/net/ethernet/mellanox/mlx5/core/en/qos.c
214baf22870cfa Maxim Mikityanskiy 2021-01-19 360
462b0059993696 Moshe Tal 2022-05-02 361 void mlx5e_reset_qdisc(struct net_device *dev, u16 qid)
214baf22870cfa Maxim Mikityanskiy 2021-01-19 362 {
214baf22870cfa Maxim Mikityanskiy 2021-01-19 363 struct netdev_queue *dev_queue = netdev_get_tx_queue(dev, qid);
214baf22870cfa Maxim Mikityanskiy 2021-01-19 @364 struct Qdisc *qdisc = dev_queue->qdisc_sleeping;
214baf22870cfa Maxim Mikityanskiy 2021-01-19 365
214baf22870cfa Maxim Mikityanskiy 2021-01-19 366 if (!qdisc)
214baf22870cfa Maxim Mikityanskiy 2021-01-19 367 return;
214baf22870cfa Maxim Mikityanskiy 2021-01-19 368
214baf22870cfa Maxim Mikityanskiy 2021-01-19 369 spin_lock_bh(qdisc_lock(qdisc));
214baf22870cfa Maxim Mikityanskiy 2021-01-19 370 qdisc_reset(qdisc);
214baf22870cfa Maxim Mikityanskiy 2021-01-19 371 spin_unlock_bh(qdisc_lock(qdisc));
214baf22870cfa Maxim Mikityanskiy 2021-01-19 372 }
214baf22870cfa Maxim Mikityanskiy 2021-01-19 373
:::::: The code at line 364 was first introduced by commit
:::::: 214baf22870cfa437522f3bd4fbae56338674b04 net/mlx5e: Support HTB offload
:::::: TO: Maxim Mikityanskiy <maximmi@mellanox.com>
:::::: CC: Jakub Kicinski <kuba@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-09-17 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 22:24 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-21 22:29 drivers/net/ethernet/mellanox/mlx5/core/en/qos.c:364:40: sparse: sparse: incorrect type in initializer (different address spaces) kernel test robot
2023-06-11 6:44 kernel test robot
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=202309180636.BDozYbf4-lkp@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.