mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <llong@redhat.com>
To: Chen Ridong <chenridong@huaweicloud.com>,
	tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	lujialin4@huawei.com, chenridong@huawei.com
Subject: Re: [PATCH -next 1/3] cpuset: simplify node setting on error
Date: Mon, 10 Nov 2025 23:26:25 -0500	[thread overview]
Message-ID: <cd1fbcd1-37e6-4aa8-8654-3305cbe085c3@redhat.com> (raw)
In-Reply-To: <20251110015228.897736-2-chenridong@huaweicloud.com>

On 11/9/25 8:52 PM, Chen Ridong wrote:
> From: Chen Ridong <chenridong@huawei.com>
>
> There is no need to jump to the 'done' label upon failure, as no cleanup
> is required. Return the error code directly instead.
>
> Signed-off-by: Chen Ridong <chenridong@huawei.com>
> ---
>   kernel/cgroup/cpuset.c | 21 +++++++++------------
>   1 file changed, 9 insertions(+), 12 deletions(-)
>
> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> index 8238fd8c0c29..c90476d52f09 100644
> --- a/kernel/cgroup/cpuset.c
> +++ b/kernel/cgroup/cpuset.c
> @@ -2897,21 +2897,19 @@ static int update_nodemask(struct cpuset *cs, struct cpuset *trialcs,
>   	 */
>   	retval = nodelist_parse(buf, trialcs->mems_allowed);
>   	if (retval < 0)
> -		goto done;
> +		return retval;
>   
>   	if (!nodes_subset(trialcs->mems_allowed,
> -			  top_cpuset.mems_allowed)) {
> -		retval = -EINVAL;
> -		goto done;
> -	}
> +			  top_cpuset.mems_allowed))
> +		return -EINVAL;
> +
> +	/* No change? nothing to do */
> +	if (nodes_equal(cs->mems_allowed, trialcs->mems_allowed))
> +		return 0;
>   
> -	if (nodes_equal(cs->mems_allowed, trialcs->mems_allowed)) {
> -		retval = 0;		/* Too easy - nothing to do */
> -		goto done;
> -	}
>   	retval = validate_change(cs, trialcs);
>   	if (retval < 0)
> -		goto done;
> +		return retval;
>   
>   	check_insane_mems_config(&trialcs->mems_allowed);
>   
> @@ -2921,8 +2919,7 @@ static int update_nodemask(struct cpuset *cs, struct cpuset *trialcs,
>   
>   	/* use trialcs->mems_allowed as a temp variable */
>   	update_nodemasks_hier(cs, &trialcs->mems_allowed);
> -done:
> -	return retval;
> +	return 0;
>   }
>   
>   bool current_cpuset_is_being_rebound(void)
Reviewed-by: Waiman Long <longman@redhat.com>


  parent reply	other threads:[~2025-11-11  4:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10  1:52 [PATCH -next 0/3] cpuset: code cleanups Chen Ridong
2025-11-10  1:52 ` [PATCH -next 1/3] cpuset: simplify node setting on error Chen Ridong
2025-11-10 14:27   ` Michal Koutný
2025-11-11  3:37     ` Chen Ridong
2025-11-11  4:26   ` Waiman Long [this message]
2025-11-11  6:16     ` Chen Ridong
2025-11-10  1:52 ` [PATCH -next 2/3] cpuset: remove global remote_children list Chen Ridong
2025-11-11  4:34   ` Waiman Long
2025-11-11  6:17     ` Chen Ridong
2025-11-10  1:52 ` [PATCH -next 3/3] cpuset: remove need_rebuild_sched_domains Chen Ridong
2025-11-11  4:37   ` Waiman Long
2025-11-11  6:18     ` Chen Ridong

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=cd1fbcd1-37e6-4aa8-8654-3305cbe085c3@redhat.com \
    --to=llong@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@huawei.com \
    --cc=chenridong@huaweicloud.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lujialin4@huawei.com \
    --cc=mkoutny@suse.com \
    --cc=tj@kernel.org \
    /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

all inboxes | Powered by JetHome®