Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	0day robot <lkp@intel.com>
Subject: kernel/cgroup/cpuset.c:3604:1: warning: unused label 'out_unlock_reset'
Date: Thu, 14 May 2026 01:34:57 +0200	[thread overview]
Message-ID: <202605140153.PDd3Fv0U-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Aaron-Tomlin/cgroup-cpuset-Fix-deadline-bandwidth-leak-in-cpuset_can_attach/20260513-233840
head:   6b7a0366d38d3efa80d721b02d588f3f519aa8b3
commit: 6c37dfa9b4198303c230c525e0796e883dde1624 cgroup/cpuset: Fix deadline bandwidth leak in cpuset_can_attach()
date:   8 hours ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260514/202605140153.PDd3Fv0U-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605140153.PDd3Fv0U-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/202605140153.PDd3Fv0U-lkp@intel.com/

All warnings (new ones prefixed by >>):

   kernel/cgroup/cpuset.c:3032:9: error: use of undeclared label 'out_unlock_reset'
    3032 |                         goto out_unlock_reset;
         |                              ^
>> kernel/cgroup/cpuset.c:3604:1: warning: unused label 'out_unlock_reset' [-Wunused-label]
    3604 | out_unlock_reset:
         | ^~~~~~~~~~~~~~~~~
   1 warning and 1 error generated.


vim +/out_unlock_reset +3604 kernel/cgroup/cpuset.c

  3563	
  3564	/*
  3565	 * In case the child is cloned into a cpuset different from its parent,
  3566	 * additional checks are done to see if the move is allowed.
  3567	 */
  3568	static int cpuset_can_fork(struct task_struct *task, struct css_set *cset)
  3569	{
  3570		struct cpuset *cs = css_cs(cset->subsys[cpuset_cgrp_id]);
  3571		bool same_cs;
  3572		int ret;
  3573	
  3574		rcu_read_lock();
  3575		same_cs = (cs == task_cs(current));
  3576		rcu_read_unlock();
  3577	
  3578		if (same_cs)
  3579			return 0;
  3580	
  3581		lockdep_assert_held(&cgroup_mutex);
  3582		mutex_lock(&cpuset_mutex);
  3583	
  3584		/* Check to see if task is allowed in the cpuset */
  3585		ret = cpuset_can_attach_check(cs);
  3586		if (ret)
  3587			goto out_unlock;
  3588	
  3589		ret = task_can_attach(task);
  3590		if (ret)
  3591			goto out_unlock;
  3592	
  3593		ret = security_task_setscheduler(task);
  3594		if (ret)
  3595			goto out_unlock;
  3596	
  3597		/*
  3598		 * Mark attach is in progress.  This makes validate_change() fail
  3599		 * changes which zero cpus/mems_allowed.
  3600		 */
  3601		cs->attach_in_progress++;
  3602		goto out_unlock;
  3603	
> 3604	out_unlock_reset:
  3605		if (cs->nr_migrate_dl_tasks)
  3606			reset_migrate_dl_data(cs);
  3607	out_unlock:
  3608		mutex_unlock(&cpuset_mutex);
  3609		return ret;
  3610	}
  3611	

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

                 reply	other threads:[~2026-05-13 23:35 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=202605140153.PDd3Fv0U-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=atomlin@atomlin.com \
    --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