From: kernel test robot <lkp@intel.com>
To: Mark Brown <broonie@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the block tree
Date: Wed, 15 Apr 2026 22:25:45 +0800 [thread overview]
Message-ID: <202604152229.1a2cJtU9-lkp@intel.com> (raw)
In-Reply-To: <adjrVagmLJaozz5o@sirena.co.uk>
Hi Mark,
kernel test robot noticed the following build errors:
[auto build test ERROR on axboe/for-next]
[also build test ERROR on isilence/zcrx/for-next]
[cannot apply to linus/master v7.0 next-20260414]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Mark-Brown/linux-next-build-failure-after-merge-of-the-block-tree/20260415-013341
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git for-next
patch link: https://lore.kernel.org/r/adjrVagmLJaozz5o%40sirena.co.uk
patch subject: linux-next: build failure after merge of the block tree
config: loongarch-randconfig-001-20260415 (https://download.01.org/0day-ci/archive/20260415/202604152229.1a2cJtU9-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260415/202604152229.1a2cJtU9-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/202604152229.1a2cJtU9-lkp@intel.com/
All errors (new ones prefixed by >>):
>> io_uring/zcrx.c:812:8: error: call to undeclared function 'netif_mp_open_rxq'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
812 | ret = netif_mp_open_rxq(ifq->netdev, if_rxq, &mp_param, NULL);
| ^
io_uring/zcrx.c:812:8: note: did you mean 'net_mp_open_rxq'?
include/net/page_pool/memory_provider.h:26:5: note: 'net_mp_open_rxq' declared here
26 | int net_mp_open_rxq(struct net_device *dev, unsigned ifq_idx,
| ^
1 error generated.
vim +/netif_mp_open_rxq +812 io_uring/zcrx.c
781
782 static int zcrx_register_netdev(struct io_zcrx_ifq *ifq,
783 struct io_uring_zcrx_ifq_reg *reg,
784 struct io_uring_zcrx_area_reg *area)
785 {
786 struct pp_memory_provider_params mp_param = {};
787 unsigned if_rxq = reg->if_rxq;
788 int ret;
789
790 ifq->netdev = netdev_get_by_index_lock(current->nsproxy->net_ns,
791 reg->if_idx);
792 if (!ifq->netdev)
793 return -ENODEV;
794
795 netdev_hold(ifq->netdev, &ifq->netdev_tracker, GFP_KERNEL);
796
797 ifq->dev = netdev_queue_get_dma_dev(ifq->netdev, if_rxq);
798 if (!ifq->dev) {
799 ret = -EOPNOTSUPP;
800 goto netdev_put_unlock;
801 }
802 get_device(ifq->dev);
803
804 ret = io_zcrx_create_area(ifq, area, reg);
805 if (ret)
806 goto netdev_put_unlock;
807
808 if (reg->rx_buf_len)
809 mp_param.rx_page_size = 1U << ifq->niov_shift;
810 mp_param.mp_ops = &io_uring_pp_zc_ops;
811 mp_param.mp_priv = ifq;
> 812 ret = netif_mp_open_rxq(ifq->netdev, if_rxq, &mp_param, NULL);
813 if (ret)
814 goto netdev_put_unlock;
815
816 ifq->if_rxq = if_rxq;
817 ret = 0;
818 netdev_put_unlock:
819 netdev_unlock(ifq->netdev);
820 return ret;
821 }
822
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-04-15 14:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <adjrVagmLJaozz5o@sirena.co.uk>]
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=202604152229.1a2cJtU9-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox