From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,oleg@redhat.com,ubizjak@gmail.com,akpm@linux-foundation.org
Subject: [folded-merged] fork-use-this_cpu_try_cmpxchg-in-try_release_thread_stack_to_cache-fix.patch removed from -mm tree
Date: Mon, 24 Jun 2024 22:22:49 -0700 [thread overview]
Message-ID: <20240625052250.00235C32782@smtp.kernel.org> (raw)
The quilt patch titled
Subject: fork-use-this_cpu_try_cmpxchg-in-try_release_thread_stack_to_cache-fix
has been removed from the -mm tree. Its filename was
fork-use-this_cpu_try_cmpxchg-in-try_release_thread_stack_to_cache-fix.patch
This patch was dropped because it was folded into fork-use-this_cpu_try_cmpxchg-in-try_release_thread_stack_to_cache.patch
------------------------------------------------------
From: Uros Bizjak <ubizjak@gmail.com>
Subject: fork-use-this_cpu_try_cmpxchg-in-try_release_thread_stack_to_cache-fix
Date: Thu, 23 May 2024 23:43:49 +0200
Simplify the for loop a bit.
Link: https://lkml.kernel.org/r/20240523214442.21102-1-ubizjak@gmail.com
Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
Cc: Oleg Nestrov <oleg@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/fork.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--- a/kernel/fork.c~fork-use-this_cpu_try_cmpxchg-in-try_release_thread_stack_to_cache-fix
+++ a/kernel/fork.c
@@ -207,9 +207,8 @@ static bool try_release_thread_stack_to_
for (i = 0; i < NR_CACHED_STACKS; i++) {
struct vm_struct *tmp = NULL;
- if (!this_cpu_try_cmpxchg(cached_stacks[i], &tmp, vm))
- continue;
- return true;
+ if (this_cpu_try_cmpxchg(cached_stacks[i], &tmp, vm))
+ return true;
}
return false;
}
_
Patches currently in -mm which might be from ubizjak@gmail.com are
fork-use-this_cpu_try_cmpxchg-in-try_release_thread_stack_to_cache.patch
reply other threads:[~2024-06-25 5:22 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=20240625052250.00235C32782@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=ubizjak@gmail.com \
/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.