From: Waiman Long <longman@redhat.com>
To: gregkh@linuxfoundation.org, mkoutny@suse.com, tj@kernel.org
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] cgroup/cpuset: Add cpuset_can_fork() and cpuset_cancel_fork()" failed to apply to 5.10-stable tree
Date: Mon, 17 Apr 2023 13:22:19 -0400 [thread overview]
Message-ID: <27aa72bf-9673-1247-e1e0-4089682173f4@redhat.com> (raw)
In-Reply-To: <2023041705-gauze-elated-d7c7@gregkh>
On 4/17/23 04:04, gregkh@linuxfoundation.org wrote:
> The patch below does not apply to the 5.10-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
>
> To reproduce the conflict and resubmit, you may use the following commands:
>
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.10.y
> git checkout FETCH_HEAD
> git cherry-pick -x eee87853794187f6adbe19533ed79c8b44b36a91
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2023041705-gauze-elated-d7c7@gregkh' --subject-prefix 'PATCH 5.10.y' HEAD^..
>
> Possible dependencies:
>
> eee878537941 ("cgroup/cpuset: Add cpuset_can_fork() and cpuset_cancel_fork() methods")
> 42a11bf5c543 ("cgroup/cpuset: Make cpuset_fork() handle CLONE_INTO_CGROUP properly")
> 18f9a4d47527 ("cgroup/cpuset: Skip spread flags update on v2")
> e2d59900d936 ("cgroup/cpuset: Allow no-task partition to have empty cpuset.cpus.effective")
> 18065ebe9b33 ("cgroup/cpuset: Miscellaneous cleanups & add helper functions")
> f9da322e864e ("cgroup: cleanup comments")
> 8ca1b5a49885 ("mm/page_alloc: detect allocation forbidden by cpuset and bail out early")
> b94f9ac79a73 ("cgroup/cpuset: Change references of cpuset_mutex to cpuset_rwsem")
> 69dc8010b8fc ("Merge branch 'for-5.15' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup")
I have posted a patch series that also include commit 18f9a4d47527
("cgroup/cpuset: Skip spread flags update on v2") which is not
technically a fix but is relative simple and low risk. I have also
twist the patches 1, 3 and 4 a bit to fit 5.10. Compile, boot and sanity
tests were done to verify its correctness.
Cheers,
Longman
prev parent reply other threads:[~2023-04-17 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 8:04 FAILED: patch "[PATCH] cgroup/cpuset: Add cpuset_can_fork() and cpuset_cancel_fork()" failed to apply to 5.10-stable tree gregkh
2023-04-17 17:22 ` Waiman Long [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=27aa72bf-9673-1247-e1e0-4089682173f4@redhat.com \
--to=longman@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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