From: Dawei Li <dawei.li@shingroup.cn>
To: catalin.marinas@arm.com, will@kernel.org
Cc: mark.rutland@arm.com, mcgrof@kernel.org, jpoimboe@kernel.org,
j.granados@samsung.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, set_pte_at@outlook.com,
Dawei Li <dawei.li@shingroup.cn>
Subject: [PATCH] arm64: remove unneeded BUILD_BUG_ON assertion
Date: Fri, 2 Feb 2024 12:02:11 +0800 [thread overview]
Message-ID: <20240202040211.3118918-1-dawei.li@shingroup.cn> (raw)
Since commit c02433dd6de3 ("arm64: split thread_info from task stack"),
CONFIG_THREAD_INFO_IN_TASK is enabled unconditionally for arm64. So
remove this always-true assertion from arch_dup_task_struct.
Signed-off-by: Dawei Li <dawei.li@shingroup.cn>
---
arch/arm64/kernel/process.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
index 7387b68c745b..4ae31b7af6c3 100644
--- a/arch/arm64/kernel/process.c
+++ b/arch/arm64/kernel/process.c
@@ -290,9 +290,6 @@ int arch_dup_task_struct(struct task_struct *dst, struct task_struct *src)
fpsimd_preserve_current_state();
*dst = *src;
- /* We rely on the above assignment to initialize dst's thread_flags: */
- BUILD_BUG_ON(!IS_ENABLED(CONFIG_THREAD_INFO_IN_TASK));
-
/*
* Detach src's sve_state (if any) from dst so that it does not
* get erroneously used or freed prematurely. dst's copies
--
2.27.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-02-02 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 4:02 Dawei Li [this message]
2024-02-05 12:06 ` [PATCH] arm64: remove unneeded BUILD_BUG_ON assertion Mark Rutland
2024-02-06 1:39 ` Dawei Li
2024-02-22 9:27 ` Dawei Li
2024-02-22 22:05 ` Catalin Marinas
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=20240202040211.3118918-1-dawei.li@shingroup.cn \
--to=dawei.li@shingroup.cn \
--cc=catalin.marinas@arm.com \
--cc=j.granados@samsung.com \
--cc=jpoimboe@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcgrof@kernel.org \
--cc=set_pte_at@outlook.com \
--cc=will@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