From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, bigeasy@linutronix.de,
andreyknvl@google.com, dan.carpenter@oracle.com,
akpm@linux-foundation.org
Subject: [folded-merged] kasan-fork-reset-pointer-tags-of-vmapped-stacks-fix-2.patch removed from -mm tree
Date: Thu, 24 Mar 2022 17:29:47 -0700 [thread overview]
Message-ID: <20220325002947.EEF16C340ED@smtp.kernel.org> (raw)
The patch titled
Subject: mm: remove unnecessary check in alloc_thread_stack_node()
has been removed from the -mm tree. Its filename was
kasan-fork-reset-pointer-tags-of-vmapped-stacks-fix-2.patch
This patch was dropped because it was folded into kasan-arm64-reset-pointer-tags-of-vmapped-stacks.patch
------------------------------------------------------
From: Dan Carpenter <dan.carpenter@oracle.com>
Subject: mm: remove unnecessary check in alloc_thread_stack_node()
The "stack" pointer cannot be NULL at this point so there is no
need to check.
Link: https://lkml.kernel.org/r/20220301080706.GB17208@kili
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Andrey Konovalov <andreyknvl@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/fork.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/kernel/fork.c~kasan-fork-reset-pointer-tags-of-vmapped-stacks-fix-2
+++ a/kernel/fork.c
@@ -328,8 +328,7 @@ static int alloc_thread_stack_node(struc
* so cache the vm_struct.
*/
tsk->stack_vm_area = vm;
- if (stack)
- stack = kasan_reset_tag(stack);
+ stack = kasan_reset_tag(stack);
tsk->stack = stack;
return 0;
}
_
Patches currently in -mm which might be from dan.carpenter@oracle.com are
kasan-arm64-reset-pointer-tags-of-vmapped-stacks.patch
reply other threads:[~2022-03-25 0:29 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=20220325002947.EEF16C340ED@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=bigeasy@linutronix.de \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.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 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.