Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v2 2/2] Squash to "bpf: Export mptcp packet scheduler helpers"
Date: Fri, 23 May 2025 02:01:48 +0800	[thread overview]
Message-ID: <202505230122.Yo10opZp-lkp@intel.com> (raw)
In-Reply-To: <dfd9d56e608ea3f68297092c9e90134e4807d3d6.1747897261.git.tanggeliang@kylinos.cn>

Hi Geliang,

kernel test robot noticed the following build errors:

[auto build test ERROR on mptcp/export]
[cannot apply to mptcp/export-net bpf-next/net bpf-next/master bpf/master linus/master v6.15-rc7 next-20250522]
[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/Geliang-Tang/Revert-selftests-bpf-Add-mptcp_subflow-bpf_iter-subtest/20250522-150813
base:   https://github.com/multipath-tcp/mptcp_net-next.git export
patch link:    https://lore.kernel.org/r/dfd9d56e608ea3f68297092c9e90134e4807d3d6.1747897261.git.tanggeliang%40kylinos.cn
patch subject: [PATCH mptcp-next v2 2/2] Squash to "bpf: Export mptcp packet scheduler helpers"
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20250523/202505230122.Yo10opZp-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250523/202505230122.Yo10opZp-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/202505230122.Yo10opZp-lkp@intel.com/

All errors (new ones prefixed by >>):

>> net/mptcp/bpf.c:334:28: error: use of undeclared identifier 'bpf_mptcp_sched_ops'
     334 |             prog->aux->st_ops != &bpf_mptcp_sched_ops)
         |                                   ^
   1 error generated.


vim +/bpf_mptcp_sched_ops +334 net/mptcp/bpf.c

   319	
   320	static int bpf_mptcp_common_kfunc_filter(const struct bpf_prog *prog, u32 kfunc_id)
   321	{
   322		if (!btf_id_set8_contains(&bpf_mptcp_common_kfunc_ids, kfunc_id))
   323			return 0;
   324	
   325		if (prog->type != BPF_PROG_TYPE_STRUCT_OPS)
   326			return -EACCES;
   327	
   328		/* .filter is called sometimes before prog->aux->st_ops is set,
   329		 * then prog->aux->st_ops is NULL. If return -EACCES in this case,
   330		 * an error occur:
   331		 * 	bug: bad parent state for iter next call
   332		 */
   333		if (prog->aux->st_ops &&
 > 334		    prog->aux->st_ops != &bpf_mptcp_sched_ops)
   335			return -EACCES;
   336	
   337		return 0;
   338	}
   339	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

           reply	other threads:[~2025-05-22 18:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <dfd9d56e608ea3f68297092c9e90134e4807d3d6.1747897261.git.tanggeliang@kylinos.cn>]

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=202505230122.Yo10opZp-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=geliang@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mptcp@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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