All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Hui Tang <tanghui20@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 2579/2579] kernel/sched/relationship.c:46:51: error: 'struct task_struct' has no member named 'mems_allowed'
Date: Sat, 14 Dec 2024 13:05:59 +0800	[thread overview]
Message-ID: <202412141314.NmcppncZ-lkp@intel.com> (raw)

tree:   https://gitee.com/openeuler/kernel.git OLK-5.10
head:   6c3413fbf8c430b89f5d23f465e10e99ea145199
commit: 2ac826b258e9aceefd719f7b0c3e3a9e73901ce5 [2579/2579] sched: Introduce task relationship by net and memory
config: arm64-randconfig-004-20241213 (https://download.01.org/0day-ci/archive/20241214/202412141314.NmcppncZ-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241214/202412141314.NmcppncZ-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/202412141314.NmcppncZ-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/linux/sched.h:23,
                    from arch/arm64/include/asm/compat.h:16,
                    from arch/arm64/include/asm/stat.h:13,
                    from include/linux/stat.h:6,
                    from include/linux/module.h:13,
                    from include/linux/bpf.h:20,
                    from include/linux/bpf_sched.h:5,
                    from kernel/sched/relationship.c:19:
   kernel/sched/relationship.c: In function 'task_relationship_supported':
>> kernel/sched/relationship.c:46:51: error: 'struct task_struct' has no member named 'mems_allowed'
      46 |                 !nodes_subset(node_online_map, tsk->mems_allowed) ||
         |                                                   ^~
   include/linux/nodemask.h:218:51: note: in definition of macro 'nodes_subset'
     218 |                         __nodes_subset(&(src1), &(src2), MAX_NUMNODES)
         |                                                   ^~~~

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for PGP_KEY_PARSER
   Depends on [n]: CRYPTO [=y] && ASYMMETRIC_KEY_TYPE [=y] && ASYMMETRIC_PUBLIC_KEY_SUBTYPE [=n]
   Selected by [y]:
   - PGP_PRELOAD [=y] && CRYPTO [=y] && ASYMMETRIC_KEY_TYPE [=y]


vim +46 kernel/sched/relationship.c

    38	
    39	bool task_relationship_supported(struct task_struct *tsk)
    40	{
    41		if (!task_relationship_used())
    42			return false;
    43	
    44		if (!tsk->rship || !tsk->mm ||
    45			!cpumask_subset(cpu_online_mask, tsk->cpus_ptr) ||
  > 46			!nodes_subset(node_online_map, tsk->mems_allowed) ||
    47			get_task_policy(tsk)->mode == MPOL_BIND ||
    48			get_task_policy(tsk)->mode == MPOL_INTERLEAVE)
    49			return false;
    50	
    51		return true;
    52	}
    53	

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

                 reply	other threads:[~2024-12-14  5:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202412141314.NmcppncZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tanghui20@huawei.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 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.