From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Waiman Long <longman@redhat.com>
Cc: stable@vger.kernel.org, "Tejun Heo" <tj@kernel.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Giuseppe Scrivano" <gscrivan@redhat.com>
Subject: Re: [PATCH 5.10 1/4] cgroup/cpuset: Change references of cpuset_mutex to cpuset_rwsem
Date: Wed, 19 Apr 2023 09:19:57 +0200 [thread overview]
Message-ID: <2023041924-endurance-chalice-9669@gregkh> (raw)
In-Reply-To: <20230417171958.3389333-1-longman@redhat.com>
On Mon, Apr 17, 2023 at 01:19:55PM -0400, Waiman Long wrote:
> Commit b94f9ac79a7395c2d6171cc753cc27942df0be73 upstream.
>
> Since commit 1243dc518c9d ("cgroup/cpuset: Convert cpuset_mutex to
> percpu_rwsem"), cpuset_mutex has been replaced by cpuset_rwsem which is
> a percpu rwsem. However, the comments in kernel/cgroup/cpuset.c still
> reference cpuset_mutex which are now incorrect.
>
> Change all the references of cpuset_mutex to cpuset_rwsem.
>
> Fixes: 1243dc518c9d ("cgroup/cpuset: Convert cpuset_mutex to percpu_rwsem")
> Signed-off-by: Waiman Long <longman@redhat.com>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
> kernel/cgroup/cpuset.c | 56 ++++++++++++++++++++++--------------------
> 1 file changed, 29 insertions(+), 27 deletions(-)
Due to all of the build problems with this series, I've now dropped all
of these from the 5.10.y queue. Please fix that up and resend if you
want to see them in this kernel release.
thanks,
greg k-h
prev parent reply other threads:[~2023-04-19 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 17:19 [PATCH 5.10 1/4] cgroup/cpuset: Change references of cpuset_mutex to cpuset_rwsem Waiman Long
2023-04-17 17:19 ` [PATCH 5.10 2/4] cgroup/cpuset: Skip spread flags update on v2 Waiman Long
2023-04-17 17:19 ` [PATCH 5.10 3/4] cgroup/cpuset: Make cpuset_fork() handle CLONE_INTO_CGROUP properly Waiman Long
2023-04-17 17:19 ` [PATCH 5.10 4/4] cgroup/cpuset: Add cpuset_can_fork() and cpuset_cancel_fork() methods Waiman Long
2023-04-19 7:19 ` Greg Kroah-Hartman [this message]
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=2023041924-endurance-chalice-9669@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=gscrivan@redhat.com \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=stable@vger.kernel.org \
--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