From: kernel test robot <lkp@intel.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [clangbuiltlinux:question_mark_operator 2/5] kernel/cgroup/cpuset.c:3768:49: error: expected expression before ';' token
Date: Sat, 12 Sep 2026 13:16:21 +0800 [thread overview]
Message-ID: <202609121317.tA4kHiVL-lkp@intel.com> (raw)
tree: https://github.com/ClangBuiltLinux/linux question_mark_operator
head: 532a7ac2d57bb5674f5feffb4ba378f8a32f3bcf
commit: b073116da78daa4548a491eba6508141a9b350dc [2/5] cgroup/cpuset: use guard(mutex) and try operator ('?') in cpuset_can_fork
config: parisc-generic-64bit_defconfig (https://download.01.org/0day-ci/archive/20260912/202609121317.tA4kHiVL-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260912/202609121317.tA4kHiVL-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/202609121317.tA4kHiVL-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/cgroup/cpuset.c: In function 'cpuset_can_fork':
>> kernel/cgroup/cpuset.c:3768:49: error: expected expression before ';' token
3768 | cpuset_can_attach_check(cs, NULL, NULL)?;
| ^
kernel/cgroup/cpuset.c:3769:31: error: expected expression before ';' token
3769 | task_can_attach(task)?;
| ^
kernel/cgroup/cpuset.c:3770:42: error: expected expression before ';' token
3770 | security_task_setscheduler(task)?;
| ^
vim +3768 kernel/cgroup/cpuset.c
3747
3748 /*
3749 * In case the child is cloned into a cpuset different from its parent,
3750 * additional checks are done to see if the move is allowed.
3751 */
3752 static int cpuset_can_fork(struct task_struct *task, struct css_set *cset)
3753 {
3754 struct cpuset *cs = css_cs(cset->subsys[cpuset_cgrp_id]);
3755 bool same_cs;
3756
3757 rcu_read_lock();
3758 same_cs = (cs == task_cs(current));
3759 rcu_read_unlock();
3760
3761 if (same_cs)
3762 return 0;
3763
3764 lockdep_assert_held(&cgroup_mutex);
3765 guard(mutex)(&cpuset_mutex);
3766
3767 /* Check to see if task is allowed in the cpuset */
> 3768 cpuset_can_attach_check(cs, NULL, NULL)?;
3769 task_can_attach(task)?;
3770 security_task_setscheduler(task)?;
3771
3772 attach_ctx.in_progress++;
3773 return 0;
3774 }
3775
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-12 5:16 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=202609121317.tA4kHiVL-lkp@intel.com \
--to=lkp@intel.com \
--cc=ndesaulniers@google.com \
--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.